...
Current implementation is (perhaps only barely) adequate for Linux/Mac as far as I know. But on Windows
- Environment is not getting propagated properly when Studio is started up from GoGui (applies only to VS 2008 since SCons only creates project and solutions files for that compiler)
- On systems with more than one compiler installed, the various setup scripts do not know anything about the environment in effect when the script was created except for certain environment variables (PATH, PYTHONPATH, etc). In particular, values for environment variables LIB and (VS 2008 only) LIBPATH are not recovered. The environment for one or another compiler can be established by running a (Microsoft-supplied) file, but exactly where the file is and what it's called depends
...
- on compiler version and also may depend on the particular installation if the user chose a non-standard install location.
2. above may doom any scheme in which the set-up file is generated once and for all by RM or, at the very least, more inputs besides GLAST_EXT and INST_DIR will be required if the set-up file is to work on remote machines.
For discussion
- pfiles - under what circumstances must the environment variable PFILES be set in the standard fashion? Is it possible to extract this task into a separate script which could be treated as source (e.g., stored in ScienceTools-scons/containerSettings), to be invoked by _setup when needed?
- what to do about set-up on machines other than the one where the _setup file was built.