diff options
author | William Deegan <bill@baddogconsulting.com> | 2019-12-17 02:42:47 (GMT) |
---|---|---|
committer | William Deegan <bill@baddogconsulting.com> | 2019-12-17 02:42:47 (GMT) |
commit | da2e57392ae9601e922b8b6f20f6faf1d708fc5a (patch) | |
tree | e2da5c0b1dd1fde9ea3f6b55c584916581f7fdd8 /README.rst | |
parent | bee7caf9defd6e108fc2998a2520ddb36a967691 (diff) | |
download | SCons-3.1.2.zip SCons-3.1.2.tar.gz SCons-3.1.2.tar.bz2 |
Updates for README and logic to upload it to Sourceforge as part of the normal upload script3.1.2
Diffstat (limited to 'README.rst')
-rwxr-xr-x | README.rst | 23 |
1 files changed, 9 insertions, 14 deletions
@@ -178,7 +178,7 @@ Or on Windows:: By default, the above commands will do the following: -- Install the version-numbered "scons-3.1.0" and "sconsign-3.0.3" scripts in +- Install the version-numbered "scons-3.1.2" and "sconsign-3.1.2" 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. @@ -190,23 +190,23 @@ By default, the above commands will do the following: 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-3.0.3" and "sconsign-3.0.3" + hard links or symbolic links to the "scons-3.1.2" and "sconsign-3.1.2" scripts by specifying the "--hardlink-scons" or "--symlink-scons" options on the command line. -- Install "scons-3.0.3.bat" and "scons.bat" wrapper scripts in the Python +- Install "scons-3.1.2.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-3.0.3.bat" and "scons.bat" files installed in the default system + have "scons-3.1.2.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-3.0.3 or - C:\\Python\*\\scons-3.0.3, for example). See below for more options related to + version-numbered SCons library directory (/usr/lib/scons-3.1.2 or + C:\\Python\*\\scons-3.1.2, 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 @@ -484,7 +484,7 @@ running all of "runtest.py -a". Building Packages ================= -We use SCons (version 3.0.3 or later) to build its own packages. If you +We use SCons (version 3.1.2 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:: @@ -613,10 +613,6 @@ LICENSE-local LICENSE with a preamble that specifies the licensing terms are for SCons itself, not any other package that includes SCons. -QMTest/ - The Python modules we use for testing, some generic modules originating - elsewhere and some specific to SCons. - README.rst What you're looking at right now. @@ -625,9 +621,6 @@ README-local Similar to this file, but stripped down and modified for people looking at including SCons in their shipped software. -rpm/ - The .spec file for building our RPM packages. - runtest.py Script for running SCons tests. By default, this will run a test against the code in the local src/ tree, so you don't have to do a build before @@ -652,6 +645,8 @@ test/ individual module unit tests, which live side-by-side with the modules under src/. +testing/ + SCons testing framework. Documentation ============= |