
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. With SCons we will be switching tagging conventions away from the current vXrYpZ standard to the new packageName-XX-YY-ZZ standard. Significantly faster if package owners help The tasks that remain for the Science Tools side are: These builds are performed for Linux in 32bit and 64bit format as well as in Windows 32bit format. The new RM is compiling packages Science Tools with SCons as the builds happen with CMT. StatusĬurrently SCons is fully functional with ScienceTools. They define the targets that SCons will create during the build process. SConscript files are the equivalent of our requirements files currently in use. This page is intended as a tutorial on getting people up to speed about the way SConscript files should be created. In short, SCons is an easier, more reliable and faster way to build software." – Think of SCons as an improved, cross-platform substitute for the classic Make utility with integrated functionality similar to autoconf/automake and compiler caches such as ccache.

"SCons is an Open Source software construction tool-that is, a next-generation build tool. It can be checked out with the command cvs co -r ScienceTools-LATEST-1-2220 ScienceTools-scons. The tag is called ScienceTools-LATEST-1-2220 and corresponds to LATEST1.2220 of CMT.

The new RM pages can be viewed from inside SLAC firewall by visiting:

To scons in terms of whether they have path in the name or not. We (mostly I) haven't been very consistent about naming the arguments Domainkey-signature: a=rsa-sha1 c=nofws d= s=gamma h=message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date:x-mailer b=Z0idFcYnITurseWcheTrUVFaiMTOVVZaIc4doGtWi33psPJOWdgDVYS18kxFYTJ+uuěJGkhvMJFwtlxzFZ1RepbNl7DqMPWvOMWR3bJh/bZocIUnUaM50Mi6Q22Nny7d60QoG7 NVyUJfSo1bpEto6MShF1xe1XlHeAc/GynN8nk=.
