Version 3.0.0
This is SCons, a tool for building software (and other files). SCons is
implemented in Python, and its "configuration files" are actually Python
scripts, allowing you to use the full power of a real scripting language
to solve build problems. You do not, however, need to know Python to
use SCons effectively.
See the RELEASE.txt file for notes about this specific release,
including known problems. See the CHANGES.txt file for a list of
changes since the previous release.
LATEST VERSION
==============
Before going further, you can check that this package you have is
the latest version by checking the SCons download page at:
http://www.scons.org/download.html
EXECUTION REQUIREMENTS
======================
INSTALLATION REQUIREMENTS
=========================
Nothing special.
INSTALLATION
============
On UNIX or Linux systems, you can have the "scons" and "sconsign"
scripts be 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.
Note that, by default, SCons does not install its build engine library
in the standard Python library directories. If you want to be able to
use the SCons library modules (the build engine) in other Python
scripts, specify the "--standard-lib" option on the command line, as
follows:
This will install the build engine in the standard Python library
directory (/usr/lib/python*/site-packages or
C:\Python*\Lib\site-packages).
Alternatively, you can have SCons install its build engine library in a
hard-coded standalone library directory, instead of the default
version-numbered directory, by specifying the "--standalone-lib" option
on the command line, as follows:
# python setup.py install --standalone-lib
DOCUMENTATION
=============
See the RELEASE.txt file for notes about this specific release,
including known problems. See the CHANGES.txt file for a list of
changes since the previous release.
The scons.1 man page is included in this package, and contains a section
of small examples for getting started using SCons.
http://www.scons.org/doc.html
LICENSING
=========
http://www.opensource.org/
REPORTING BUGS
==============
http://scons.tigris.org/bug-submission.html
You can also send mail to the SCons developers' mailing list:
scons-dev@scons.org
But even if you send email to the mailing list please make sure that you
ALSO submit a bug report to the project page bug tracker, because bug
reports in email often get overlooked in the general flood of messages.
MAILING LISTS
=============
An active mailing list for users of SCons is available. You may send
questions or comments to the list at:
scons-users@scons.org
scons-users-join@scons.org
announce-subscribe@scons.tigris.org
There are other mailing lists available for SCons developers, for
notification of SCons code changes, and for notification of updated
bug reports and project documents. Please see our mailing lists page
for details.
DONATIONS
=========
If you find SCons helpful, please consider making a donation (of cash,
software, or hardware) to support continued work on the project.
Information is available at:
http://www.scons.org/donate.html
http://www.scons.org/
AUTHOR INFO
===========
SCons was originally written by Steven Knight, knight at baldmt dot com.
Since around 2010 it has been maintained by the SCons
development team, co-managed by Bill Deegan and Gary Oberbrunner, with
many contributors, including but not at all limited to:
- Chad Austin
- Dirk Baechle
- Charles Crain
- William Deegan
- Steve Leblanc
- Rob Managan
- Greg Noel
- Gary Oberbrunner
- Anthony Roach
- Greg Spencer
- Tom Tanner
- Anatoly Techtonik
- Christoph Wiedemann
- Russel Winder