-- (Optional.) Install from a pre-packaged SCons package that
does not require distutils:
- Red Hat Linux scons-1.0.0.noarch.rpm
+ Red Hat Linux scons-1.0.1.noarch.rpm
Debian GNU/Linux use apt-get to get the official package
- Windows scons-1.0.0.win32.exe
+ Windows scons-1.0.1.win32.exe
-- (Recommended.) Download the latest distutils package from the
following URL:
By default, the above commands will do the following:
- -- Install the version-numbered "scons-1.0.0" and "sconsign-1.0.0"
+ -- Install the version-numbered "scons-1.0.1" and "sconsign-1.0.1"
scripts in the default system script directory (/usr/bin or
C:\Python*\Scripts, for example). This can be disabled by
specifying the "--no-version-script" option on the command
making it the default on your system.
On UNIX or Linux systems, you can have the "scons" and "sconsign"
- scripts be hard links or symbolic links to the "scons-1.0.0" and
- "sconsign-1.0.0" scripts by specifying the "--hardlink-scons" or
+ scripts be hard links or symbolic links to the "scons-1.0.1" and
+ "sconsign-1.0.1" scripts by specifying the "--hardlink-scons" or
"--symlink-scons" options on the command line.
- -- Install "scons-1.0.0.bat" and "scons.bat" wrapper scripts in the
+ -- Install "scons-1.0.1.bat" and "scons.bat" wrapper scripts in the
Python prefix directory on Windows (C:\Python*, for example).
This can be disabled by specifying the "--no-install-bat" option
on the command line.
On UNIX or Linux systems, the "--install-bat" option may be
- specified to have "scons-1.0.0.bat" and "scons.bat" files installed
+ specified to have "scons-1.0.1.bat" and "scons.bat" files installed
in the default system script directory, which is useful if you
want to install SCons in a shared file system directory that can
be used to execute SCons from both UNIX/Linux and Windows systems.
-- Install the SCons build engine (a Python module) in an
appropriate version-numbered SCons library directory
- (/usr/lib/scons-1.0.0 or C:\Python*\scons-1.0.0, for example).
+ (/usr/lib/scons-1.0.1 or C:\Python*\scons-1.0.1, for example).
See below for more options related to installing the build
engine library.
Depending on the utilities installed on your system, any or all of the
following packages will be built:
- build/dist/scons-1.0.0-1.noarch.rpm
- build/dist/scons-1.0.0-1.src.rpm
- build/dist/scons-1.0.0.linux-i686.tar.gz
- build/dist/scons-1.0.0.tar.gz
- build/dist/scons-1.0.0.win32.exe
- build/dist/scons-1.0.0.zip
- build/dist/scons-doc-1.0.0.tar.gz
- build/dist/scons-local-1.0.0.tar.gz
- build/dist/scons-local-1.0.0.zip
- build/dist/scons-src-1.0.0.tar.gz
- build/dist/scons-src-1.0.0.zip
- build/dist/scons_1.0.0-1_all.deb
+ build/dist/scons-1.0.1-1.noarch.rpm
+ build/dist/scons-1.0.1-1.src.rpm
+ build/dist/scons-1.0.1.linux-i686.tar.gz
+ build/dist/scons-1.0.1.tar.gz
+ build/dist/scons-1.0.1.win32.exe
+ build/dist/scons-1.0.1.zip
+ build/dist/scons-doc-1.0.1.tar.gz
+ build/dist/scons-local-1.0.1.tar.gz
+ build/dist/scons-local-1.0.1.zip
+ build/dist/scons-src-1.0.1.tar.gz
+ build/dist/scons-src-1.0.1.zip
+ build/dist/scons_1.0.1-1_all.deb
The SConstruct file is supposed to be smart enough to avoid trying to
build packages for which you don't have the proper utilities installed.