Organizing Your Workspace

There are 3 tiers to the code when using Gleam:

Gaudi
Gleam
your stuff

It is worth noting that they are listed above in terms of stability. Gaudi changes rarely, but Gleam changes a fair bit. That's why it is convenient for you to separate your code from it.

For example (version numbers will change of course) - create separate directories for:

GaudiSys_v9 - keep GaudiSys and add minor revisions as they come out
Gleam_v2 - keep Gleam
myProject - your stuff
- it can include userAlg or your own jobOptions or your own versions of packages
- you can have any number of them in parallel. Each could have its own userAlg looking at different things

The CMTPATH order would be myProject: Gleam: GaudiSys, so that your stuff comes first in the search order.

eg on linux, a sample CMTPATH file could look like:

CMTPATH=/nfs/slac/g/glast/users/glground/richard/glastPackTest/memLeak:

/nfs/slac/g/glast/users/glground/richard/glastPackTest/Gleam_v2r3p1:/nfs/slac/g/glast/users/glground/richard/glastPackTest/GaudiSys_v9r0p5:

Or in vcmt (myProject morphs to RandomsTest)

c:\glast\pdr\Gleam\RandomsTest
c:\glast\pdr\Gleam\Gleam_v2r3p1
c:\glast\pdr\Gleam\GaudiSys_v9r0p5

So, one would

recursively checkout GaudiSys into its directory and build it
ditto for Gleam.
ditto myProject

R.Dubois Last Modified: 2004-08-04 15:39:18 -0700