summaryrefslogtreecommitdiff
path: root/README.rst
diff options
context:
space:
mode:
authorJörg Frings-Fürst <debian@jff-webhosting.net>2016-04-10 18:15:03 +0200
committerJörg Frings-Fürst <debian@jff-webhosting.net>2016-04-10 18:15:03 +0200
commit301edd26f23e3d954dcea5cffc1ad13f969822ca (patch)
treeb0dd8f1b1da7c48da076ae45fc9529e748d082f0 /README.rst
parente20c9557371eacec533588d33b4bebd543ba178f (diff)
Imported Upstream version 2.5.0+repackupstream/2.5.0+repack
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst50
1 files changed, 31 insertions, 19 deletions
diff --git a/README.rst b/README.rst
index a2b15a6..ba1755f 100644
--- a/README.rst
+++ b/README.rst
@@ -1,6 +1,18 @@
SCons - a software construction tool
####################################
+.. image:: https://img.shields.io/badge/IRC-scons-blue.svg
+ :target: http://webchat.freenode.net/?channels=%23scons&uio=d4
+ :alt: IRC
+
+.. image:: https://img.shields.io/sourceforge/dm/scons.svg
+ :target: https://sourceforge.net/projects/scons
+ :alt: Sourceforge Monthly Downloads
+
+.. image:: https://img.shields.io/sourceforge/dt/scons.svg
+ :target: https://sourceforge.net/projects/scons
+ :alt: Sourceforge Total Downloads
+
Welcome to the SCons development tree. The real purpose of this tree is to
package SCons for production distribution in a variety of formats, not just to
hack SCons code.
@@ -156,7 +168,7 @@ Or on Windows::
By default, the above commands will do the following:
-- Install the version-numbered "scons-2.4.1" and "sconsign-2.4.1" scripts in
+- Install the version-numbered "scons-2.5.0" and "sconsign-2.5.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.
@@ -168,23 +180,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-2.4.1" and "sconsign-2.4.1"
+ hard links or symbolic links to the "scons-2.5.0" and "sconsign-2.5.0"
scripts by specifying the "--hardlink-scons" or "--symlink-scons" options on
the command line.
-- Install "scons-2.4.1.bat" and "scons.bat" wrapper scripts in the Python
+- Install "scons-2.5.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.4.1.bat" and "scons.bat" files installed in the default system
+ have "scons-2.5.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.4.0 or
- C:\\Python\*\\scons-2.4.0, for example). See below for more options related to
+ 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
installing the build engine library.
- Install the troff-format man pages in an appropriate directory on UNIX or
@@ -462,7 +474,7 @@ running all of "runtest.py -a".
Building Packages
=================
-We use SCons (version 2.4.1 or later) to build its own packages. If you
+We use SCons (version 2.5.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::
@@ -477,18 +489,18 @@ about `Executing SCons Without Installing`_)::
Depending on the utilities installed on your system, any or all of the
following packages will be built::
- build/dist/scons-2.4.1-1.noarch.rpm
- build/dist/scons-2.4.1-1.src.rpm
- build/dist/scons-2.4.1.linux-i686.tar.gz
- build/dist/scons-2.4.1.tar.gz
- build/dist/scons-2.4.1.win32.exe
- build/dist/scons-2.4.1.zip
- build/dist/scons-doc-2.4.1.tar.gz
- build/dist/scons-local-2.4.1.tar.gz
- build/dist/scons-local-2.4.1.zip
- build/dist/scons-src-2.4.1.tar.gz
- build/dist/scons-src-2.4.1.zip
- build/dist/scons_2.4.1-1_all.deb
+ 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-2.5.0.tar.gz
+ build/dist/scons-2.5.0.win32.exe
+ build/dist/scons-2.5.0.zip
+ build/dist/scons-doc-2.5.0.tar.gz
+ build/dist/scons-local-2.5.0.tar.gz
+ build/dist/scons-local-2.5.0.zip
+ build/dist/scons-src-2.5.0.tar.gz
+ build/dist/scons-src-2.5.0.zip
+ build/dist/scons_2.5.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