...
This page is intended as a tutorial on getting people up to speed about the way SConscript files should be created. SConscript files are the equivalent of our requirements files currently in use. They define the targets that SCons will create during the build process.
Status
Currently SCons is fully functional with ScienceTools. The new RM is compiling packages Science Tools with SCons as the builds happen with CMT. These builds are performed for Linux in 32bit and 64bit format as well as in Windows 32bit format. The tasks that remain for the Science Tools side are:
Task | Status | Time Estimate | Comments |
|---|---|---|---|
Fix of last few unit test failures. | No progress | Unknown | Package owners need to take active role in this |
New tag collector to use with SCons. | Work in Progress. 50% Done. | 2-3 Weeks |
|
New MrStudio replacement for SCons. | No Progress | Several weeks to a Month | This will heavily rely on the tag collector |
Port to new OSes | Some Progress but on hold for now | Unknown |
|
On the GlastRelease side there is no progress yet. ScienceTools design can be used under GlastRelease and will accomplish 90% of GlastRelease's needs. The other 10% of the tasks that remain are:
Task | Status | Time Estimate | Comments |
|---|---|---|---|
Create special SCons builder for gaudi | No Progress | 1-2 Weeks |
|
Create SConscript files for all packages | No Progress | 2-3 Weeks | Significantly faster if package owners help |
Modify new RM to build GlastRelease | No Progress | 1-2 Weeks |
|
Tagging convention
With SCons we will be switching tagging conventions away from the current vXrYpZ standard to the new packageName-XX-YY-ZZ standard. What this means is that any package performing a tag will have to have their package name in the tag as well as use only 2 digit version numbering. For example if in the old convention the Likelihood package would apply the tag v1r2p3, in the new convention this tag would be Likelihood-01-02-03. This convention is currently automatically enforced by the old RM. Whenever a package is tagged with the vXrYpZ format, the old RM automatically tags the same package with packageName-XX-YY-ZZ. In the near future this convention will be reversed.
...