...
Joanne explained the thinking behind Tom's work to automate the determination of the path to set up the environment based on the type of OS desired for a run. It is desired to automate this setup, to prepare the a path to the setup script suitable for the desired combination of variant, debug/opt,etc. Joanne feels providing a central utility is the way to go. Navid is willing to help out. Tom has created a python script as a starting point:
Wiki Markup
- Script is currently stored here: /u/ec/dragon/bin/svs.py
- Various SCons-related strings can be constructed
- Lots of parameter overrides so that one may 'force' a particular SCons config independent of the machine being used.
- Acts as a stand-alone python app, or a python function - both return a single string
- Currently limited to ScienceTools builds
- built-in help:
...
- Example: how to use svs.py to set up one's environment to run ScienceTools.
- Add this to your .bashrc (SCons does not provide a C-shell setup script for ScienceTools 09-15-03 so one is obligated to use bash)
Code Block export SCONS_ARCH=`/u/ec/dragon/bin/svs.py -s` export SCONS_BIN=`/u/ec/dragon/bin/svs.py -b` export INST_DIR=`/u/ec/dragon/bin/svs.py -i` export GLAST_EXT=/afs/slac/g/glast/ground/GLAST_EXT/${SCONS_ARCH} - When ready to run ScienceTools, run the official setup script (either manually or put this into .bashrc after the above lines)
Code Block source $SCONS_BIN/_setup.sh
- Add this to your .bashrc (SCons does not provide a C-shell setup script for ScienceTools 09-15-03 so one is obligated to use bash)
...
\[end of TG update\]
Tom also noted that the different directory structures in the old-style GLAST_EXT for CMT externals and the SCons version causes some trouble when attempting to set up for both ST and GR. We could provide symlinks across the board for the GR externals to standardize the setup. This will probably also be taken care of as we move to support GR SCons builds.