...

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.

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.

Minimal SConscript file

This example shows a minimal SConscript file. It will build nothing but will import some of the tools necessary for when we add targets to be built. It should be stored in the top level directory of the package.

...