SCONSIGN(1) | SCons __VERSION__ | SCONSIGN(1) |
sconsign - print SCons signature file information
sconsign [options...] [file...]
Displays the contents of one or more sconsign files, the signature database files used by the SCons build tool.
By default, sconsign dumps the entire contents of the sconsign file(s). Without options, individual dependency entries are printed in the following format:
depfile: signature timestamp length
implicit_dependency_1: content_signature timestamp length
implicit_dependency_2: content_signature timestamp length
...
action_signature [action string]
None is printed in place of any missing timestamp, content signature (csig) or build action signature values for any entry or any of its dependencies. If the entry has no implicit dependencies, or no build action, those lines are omitted.
By default, sconsign assumes that any file arguments that end with a .dblite suffix contains signature entries for more than one directory (that is, was specified by the SConsignFile function). Any file argument that has no suffix is assumed to be an old-style sconsign file containing the signature entries for a single directory. If neither of those is true, sconsign attempts to guess the format. If that does not work, an explicit format may be specified using the -f or --format= options.
If there are no file arguments, the name .sconsign.dblite is assumed by default.
Various options control what information is printed and the format:
-a, --act, --action
-c, --csig
-d DIRECTORY, --dir=DIRECTORY
-e ENTRY, --entry=ENTRY
-f FORMAT, --format=FORMAT
-h, --help
-i, --implicit
--raw
-r, --readable
-t, --timestamp
-v, --verbose
SCONS_LIB_DIR
scons, the SCons User Guide at https://scons.org/doc/production/HTML/scons-user.html, the SCons source code on GitHub[1].
Originally: Steven Knight knight@baldmt.com and Anthony Roach aroach@electriceyeball.com.
Since 2010: The SCons Development Team scons-dev@scons.org.
09/20/2022 | SCons __VERSION__ |