SCons

SCons software history started with the Cons software construction utility created by Bob Sidebotham in 1999.^[3] Cons was written in the Perl language. It served as a base for the ScCons build tool, a design which won the Software Carpentry project SC Build competition in August 2000.^[4] ScCons was the foundation for SCons.

SCons inspired the creation of Waf, formerly known as SCons/BKsys, which emerged in the KDE community. For some time, there were plans to use it as the build tool for KDE 4 and beyond, but that effort was abandoned in favor of CMake.^[5]

Notable applications that use SCons include the following: The Battle for Wesnoth,^[6] Battlefield 1942,^{[citation needed]} Doom 3,^[7] FCEUX,^[8] gem5,^[9] gpsd,^[10] GtkRadiant,^[11] Madagascar,^[12] Mixxx,^[13] MongoDB,^[14] Nullsoft Scriptable Install System,^[15] OpenNebula,^[16] VMware,^{[citation needed]}, Wolfenstein: Enemy Territory,^[17] XORP and MCA2,^[18] openpilot^[19] and Godot.^[20]

.csig is the SCons Content Signature file format.

Major SCons features include the following:

• Configuration files are Python scripts, which means that user-written builds have access to a complete general-purpose programming language.
• Automatic dependency analysis built-in for C, C++ and Fortran. Dependency analysis is extensible through user-defined dependency scanners for other languages or file types. Unlike the GNU Compiler Collection's (GCC) built-in dependency analysis, it uses a regular expression scan for included source files.
• Built-in support for C, C++, D, Java, Fortran, Objective-C, Yacc, Lex, Qt and SWIG, as well as TeX and LaTeX documents. SCons can also handle other languages or file types through user-defined builders.
• Building from central repositories of source code and pre-built targets.
• Built-in ability to use Microsoft Visual Studio, including the generation of .dsp, .dsw, .sln and .vcproj files.
• Detection of file content changes using MD5 signatures; optional, configurable ability to use traditional timestamps.
• Ability to do parallel builds, maintaining a specified number of jobs running simultaneously regardless of directory hierarchy.
• Integrated Autoconf-like support for finding #include files, libraries, functions and typedefs.
• Global view of all dependencies, so multiple build passes or reordering targets is not required.
• Ability to share built files in a cache to speed up multiple builds - like ccache but for any type of target file, not just C/C++ compilation.
• Designed from the ground up for cross-platform builds, and known to work on POSIX systems (including Linux, IBM AIX and OS/2, *BSD Unices, HP-UX, SGI IRIX, Solaris, illumos), MS Windows NT, Apple OS X.

The following example is a very simple SConstruct file that compiles the C program file hello-world.c using the default platform compiler:

Program("hello-world.c")

The following is a more complex example that creates an environment used to build the program hello:

env = Environment()
env.Append(CPPFLAGS=["-Wall", "-g"])
env.Program("hello",
            ["hello.c", "main.c"])

• Buildout
• CMake
• qmake
• Qbs (build tool)
• Premake
• GNU build system
• List of build automation software
• Waf

• Official website