...
Jim reminded us that it would be helpful to provide a mechanism for tags such as rh9_gcc32 and rhel4, similarly for opt and debug builds. Navid could implement subdirectories with expanded English names as he's found some users are confused by our use of rh9_gcc32 for instance, something like redhat9_optimized.
Toby made a request that the new RM avoid "big bang builds" which take oodles of time. He suggested that packages common to both ST and GR could be pulled into their own checkout package. Navid stated that the SCons builds are much faster than the CMT builds.
Visual Studio 2005 - Toby is hoping Riccardo can fix up MRvcmt to use his python scripts to work with VS2005. Or perhaps MRvcmt is considered frozen - we need to discuss this with Riccardo as soon as possiblee.
Defining Applications using Likelihood as an example
...
Eric Winter, on behalf of the Science Support Center, asked about the future of the CMT requirements files. Currently hmake reads in the requirements files to set up its builds of the science tools. We plan to keep the CMT requirements file for about six months, as we continue to prepare for our move to SCons. We will have to provide some replacement, some SCons tool, for the GSSC to use instead. Currently, the SConscript and <package>Lib.py files contain the same information as the CMT requirements files. Brian Irby is man in charge of hmake.
To Do List
- Finish demonstration of SCons using ScienceTools, including over-riding packaegs / multiple CMTPATHs
- Windows and Visual Studio
- Use commonUtilities to replace our current use of environment variables
- Create ScienceTools-scons in CVS
- Create a new RM which is separate from our current one.
- Determine the schedule for MRStudio and what is necessary for the SCons-world.