...
| Wiki Markup |
|---|
The code CVS repository reside at the $CVSROOT/users/Trg/\[Packagename\] (CVSROOT is /afs/slac/g/glast/ground/cvs on SLAC UNIX). As part of the "users" code, they are not attached to any office release so that you need to check them out and compile yourself for all usage. Because the packages live under users/ subdirectories, some care needs to be taken to not accidentally checkout or tag the whole users package with many people's code (you will regret it\!). The general usage of the users packages are eplianed by Toby in [this posting|http://www-glast.stanford.edu/protected/mail/infrasoft/0852.html]. As an example, if you want to develop the TrgTest code, starting from tag v0-01, under your own release directory _myRelease,_ then the cvs checkout command is:
cd myRelease
cvs co \-r v0-01 \-o users/Trg TrgTest
The \-o option indicates the directory offset for the package. This should make a directory myRelease/TrgTest/v0-01/. Within the package directory, you typically should have a subdirectory with the same name as the package name which contains the class headers; a subdirectory /src containging the class implementation C+\+ source files and the /cmt subdirectory containing the build options. The TrgTest pacakge also has a subdirectory /workdir for running applications in ROOT. When you commit the revised version for Trgtest, you should also issue the cvs commit from the directory myRelease/TrgTest/v0-00/ or it subdirectories to only commit code within the package. When you want to tag an updated version, again you should be sitting in myRelease/TrgTest/v0-01/ and using the \-rtag recommended by Toby for the packages residing in subdirectories:
cvs rtag _TagName_ users/Trg/TrgTest |
CMT Code Build
For packages checked out from CVS, you will work within CMT to build and update them. The The interactive CMT GUI is the recommended tool for doing development. It can be started with the command MRvcmt& after the setup is run. The essense of the CMT operations are introduced in the offline workbookunder the tab: MRvcmt. Use the Options->Cmt Options tab Upon startup of MRvcmt for the first time you need to configure the paths. From the MRvcmt top menu, select the Options tab then "Cmt Options" to bring up the the following panel: !snap-cmt-options!
to control the CMT path directories. You can also check what's in /afs/slac/g/glast/trigger/GlastRelease/cmtpath-save as an example how this is setup for development work in this working area. One typically goes to the GUI GlastRelease folder RTAutil or TrgTest package (by click and highlighting it) then just work under the Dev tab clean/config/Make to build and update the ROOT sharable libraries.
...