SCons
Original author(s)Steven Knight
Stable release
4.4.0[1] / July 31, 2022 (2022-07-31)
Repositorygithub.com/SCons/scons
Written inPython
Operating systemCross-platform
TypeSoftware development tools
LicenseMIT License
Websitescons.org

SCons is a computer software build tool that automatically analyzes source code file dependencies and operating system adaptation requirements from a software project description and generates final binary executables for installation on the target operating system platform. Its function is analogous to the traditional GNU build system based on the make utility and the autoconf tools.

SCons generates project configurations and build process implementations in the form of Python scripts.

SCons software history started with the Cons software construction utility created by Bob Sidebotham in 1999.[2] 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.[3] 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.[4]

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

.csig is the SCons Content Signature file format.

Major features

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.

Examples

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"])

See also

References

  1. ↑ "Archives - SCons".
  2. ↑ Cons (web site), DSMit, archived from the original on 2000-08-15.
  3. ↑ Samuel, Alex (2000-08-04). "Software Carpentry Design Competition Second Round Results Config, Build, and Track categories". Retrieved 2012-10-29.
  4. ↑ Neundorf, Alexander (21 June 2006). "Why the KDE project switched to CMake – and how (continued)". LWN. Retrieved 21 July 2009.
  5. ↑ "CompilingWesnoth". Wiki. Wesnoth. Retrieved 2011-04-11.
  6. ↑ "README.txt". id Software. Retrieved 2015-05-13.
  7. ↑ "Downloads". FCEUX. Retrieved 2017-04-25.
  8. ↑ Gem5.
  9. ↑ "SCons is full of win today". ESR. iBiblio. 2011-04-05. Retrieved 2011-04-11.
  10. ↑ "Developer documentation for GtkRadiant 1.6.0 (Zeroradiant)" (Trac). QE radiant. 2008-06-30. Retrieved 2009-12-28.
  11. ↑ "Installation". Wiki. Ahay. 2011-02-26. Retrieved 2011-04-11.
  12. ↑ "Mixxx/Compiling". GitHub. 2014-08-26.
  13. ↑ "Building for Linux". MongoDB. 10gen. January 30, 2009. Archived from the original on February 21, 2009. Retrieved February 8, 2011.
  14. ↑ "INSTALL". NSIS (source code). Source forge. 2011-05-28. Archived from the original on 2012-07-11. Retrieved 2011-04-11.
  15. ↑ "/SConstruct - OpenNebula - OpenNebula Development pages". OpenNebula Project. Retrieved 2016-01-09.
  16. ↑ "README.txt". id Software. Retrieved 2017-04-25.
  17. ↑ "Modular Controller Architecture". Research Center for Information Technology (FZI), Karlsruhe Institute of Technology (KIT).
  18. ↑ "openpilot Github repository". comma.ai/. Retrieved 2021-05-10.
  19. ↑ "Introduction to the buildsystem — Godot Engine latest documentation". docs.godotengine.org. Retrieved 2019-08-19.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.