By default, the above commands will do the following:
-- Install the version-numbered "scons-2.5.0" and "sconsign-2.5.0" scripts in
+- Install the version-numbered "scons-3.0.0" and "sconsign-3.0.0" 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 line.
before 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-2.5.0" and "sconsign-2.5.0"
+ hard links or symbolic links to the "scons-3.0.0" and "sconsign-3.0.0"
scripts by specifying the "--hardlink-scons" or "--symlink-scons" options on
the command line.
-- Install "scons-2.5.0.bat" and "scons.bat" wrapper scripts in the Python
+- Install "scons-3.0.0.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-2.5.0.bat" and "scons.bat" files installed in the default system
+ have "scons-3.0.0.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-2.5.0 or
- C:\\Python\*\\scons-2.5.0, for example). See below for more options related to
+ version-numbered SCons library directory (/usr/lib/scons-3.0.0 or
+ C:\\Python\*\\scons-3.0.0, for example). See below for more options related to
installing the build engine library.
- Install the troff-format man pages in an appropriate directory on UNIX or
Building Packages
=================
-We use SCons (version 2.5.0 or later) to build its own packages. If you
+We use SCons (version 3.0.0 or later) to build its own packages. If you
already have an appropriate version of SCons installed on your system, you can
build everything by simply running it::
Depending on the utilities installed on your system, any or all of the
following packages will be built::
- build/dist/scons-2.5.0-1.noarch.rpm
- build/dist/scons-2.5.0-1.src.rpm
- build/dist/scons-2.5.0.linux-i686.tar.gz
- build/dist/scons-3.0.0.alpha.20170821.tar.gz
- build/dist/scons-3.0.0.alpha.20170821.win32.exe
- build/dist/scons-3.0.0.alpha.20170821.zip
- build/dist/scons-doc-3.0.0.alpha.20170821.tar.gz
- build/dist/scons-local-3.0.0.alpha.20170821.tar.gz
- build/dist/scons-local-3.0.0.alpha.20170821.zip
- build/dist/scons-src-3.0.0.alpha.20170821.tar.gz
- build/dist/scons-src-3.0.0.alpha.20170821.zip
- build/dist/scons_3.0.0.alpha.20170614-1_all.deb
+ build/dist/scons-3.0.0-1.noarch.rpm
+ build/dist/scons-3.0.0-1.src.rpm
+ build/dist/scons-3.0.0.linux-i686.tar.gz
+ build/dist/scons-3.0.0.tar.gz
+ build/dist/scons-3.0.0.win32.exe
+ build/dist/scons-3.0.0.zip
+ build/dist/scons-doc-3.0.0.tar.gz
+ build/dist/scons-local-3.0.0.tar.gz
+ build/dist/scons-local-3.0.0.zip
+ build/dist/scons-src-3.0.0.tar.gz
+ build/dist/scons-src-3.0.0.zip
+ build/dist/scons_3.0.0-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. For
Additional documentation for SCons is available at:
- http://www.scons.org/documentation.php
+ http://www.scons.org/documentation
Licensing
software, or hardware) to support continued work on the project. Information
is available at:
- http://www.scons.org/donate.php
+ http://www.scons.org/donate.html
For More Information
\... and many others.
-Copyright (c) 2001 - 2015 The SCons Foundation
+Copyright (c) 2001 - 2017 The SCons Foundation
Change Log
-RELEASE 3.0.0.alpha.20170821 - Mon, 21 Aug 2017 16:15:02 -0700
+RELEASE 3.0.0 - Mon, 18 Sep 2017 08:32:04 -0700
NOTE: This is a major release. You should expect that some targets may rebuild when upgrading.
-Significant changes in some python action signatures. Also switching between PY 2 and PY 3.5, 3.6
-may cause rebuilds. In no case should rebuilds not happen.
+Significant changes in some python action signatures. Also switching between PY 2.7 and PY 3.5, 3.6
+will cause rebuilds.
From William Blevins:
"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe"
It can be downloaded separately at
https://github.com/Microsoft/vswhere
+
+ From Tom Tanner:
+ - Allow nested $( ... $) sections
From Paweł Tomulik:
- Fixed the issue with LDMODULEVERSIONFLAGS reported by Tim Jenness
tools, must now include the ar tool to get this builder as is required for
other compiler tools.
- Add clang and clang++ tools based on Paweł Tomulik's work.
-
- From Tom Tanner:
- - Allow nested $( ... $) sections
RELEASE 2.5.1 - Mon, 03 Nov 2016 13:37:42 -0400