%scons; %builders-mod; %functions-mod; %tools-mod; %variables-mod; ]>

A dictionary mapping the names of the builders available through the &consenv; to underlying Builder objects. Custom builders need to be added to this to make them available. A platform-dependent default list of builders such as &b-link-Program;, &b-link-Library; etc. is used to populate this &consvar; when the &consenv; is initialized via the presence/absence of the tools those builders depend on. &cv-BUILDERS; can be examined to learn which builders will actually be available at run-time. Note that if you initialize this &consvar; through assignment when the &consenv; is created, that value for &cv-BUILDERS; will override any defaults: bld = Builder(action='foobuild < $SOURCE > $TARGET') env = Environment(BUILDERS={'NewBuilder': bld}) To instead use a new Builder object in addition to the default Builders, add your new Builder object like this: env = Environment() env.Append(BUILDERS={'NewBuilder': bld}) or this: env = Environment() env['BUILDERS']['NewBuilder'] = bld

The execution environment - a dictionary of environment variables used when &SCons; invokes external commands to build targets defined in this &consenv;. When &cv-ENV; is passed to a command, all list values are assumed to be path lists and are joined using the search path separator. Any other non-string values are coerced to a string. Note that by default &SCons; does not propagate the environment in effect when you execute &scons; (the "shell environment") to the execution environment. This is so that builds will be guaranteed repeatable regardless of the environment variables set at the time &scons; is invoked. If you want to propagate a shell environment variable to the commands executed to build target files, you must do so explicitly. A common example is the system &PATH; environment variable, so that &scons; will find utilities the same way as the invoking shell (or other process): import os env = Environment(ENV={'PATH': os.environ['PATH']}) Although it is usually not recommended, you can propagate the entire shell environment in one go: import os env = Environment(ENV=os.environ.copy())

A list of the available implicit dependency scanners. New file scanners may be added by appending to this list, although the more flexible approach is to associate scanners with a specific Builder. See the manpage sections "Builder Objects" and "Scanner Objects" for more information.

A reserved variable name that may not be set or used in a &consenv;. (See the manpage section "Variable Substitution" for more information).

A list of the names of the Tool specification modules that were actually initialized in the current &consenv;. This may be useful as a diagnostic aid to see if a tool did (or did not) run. The value is informative and is not guaranteed to be complete.

The class type that SCons should use when instantiating a new &f-link-CacheDir; in this &consenv;. Must be a subclass of the SCons.CacheDir.CacheDir class.

(action, [output, [var, ...]] [key=value, ...])

A factory function to create an Action object for the specified action. See the manpage section "Action Objects" for a complete explanation of the arguments and behavior. Note that the &f-env-Action; form of the invocation will expand &consvars; in any argument strings, including the action argument, at the time it is called using the &consvars; in the &consenv; through which &f-env-Action; was called. The &f-Action; global function form delays all variable expansion until the Action object is actually used.

(object, function, [name]) (function, [name])

Adds function to an object as a method. function will be called with an instance object as the first argument as for other methods. If name is given, it is used as the name of the new method, else the name of function is used. When the global function &f-AddMethod; is called, the object to add the method to must be passed as the first argument; typically this will be &Environment;, in order to create a method which applies to all &consenvs; subsequently constructed. When called using the &f-env-AddMethod; form, the method is added to the specified &consenv; only. Added methods propagate through &f-env-Clone; calls. More examples: # Function to add must accept an instance argument. # The Python convention is to call this 'self'. def my_method(self, arg): print("my_method() got", arg) # Use the global function to add a method to the Environment class: AddMethod(Environment, my_method) env = Environment() env.my_method('arg') # Use the optional name argument to set the name of the method: env.AddMethod(my_method, 'other_method_name') env.other_method_name('another arg')

(target, action)

Arranges for the specified action to be performed after the specified target has been built. action may be an Action object, or anything that can be converted into an Action object. See the manpage section "Action Objects" for a complete explanation. When multiple targets are supplied, the action may be called multiple times, once after each action that generates one or more targets in the list. foo = Program('foo.c') # remove execute permission from binary: AddPostAction(foo, Chmod('$TARGET', "a-x"))

(target, action)

Arranges for the specified action to be performed before the specified target is built. action may be an Action object, or anything that can be converted into an Action object. See the manpage section "Action Objects" for a complete explanation. When multiple targets are specified, the action(s) may be called multiple times, once before each action that generates one or more targets in the list. Note that if any of the targets are built in multiple steps, the action will be invoked just before the "final" action that specifically generates the specified target(s). For example, when building an executable program from a specified source .c file via an intermediate object file: foo = Program('foo.c') AddPreAction(foo, 'pre_action') The specified pre_action would be executed before &scons; calls the link command that actually generates the executable program binary foo, not before compiling the foo.c file into an object file.

(alias, [source, [action]])

Creates an alias target that can be used as a reference to zero or more other targets, specified by the optional source parameter. Aliases provide a way to give a shorter or more descriptive name to specific targets, and to group multiple targets under a single name. The alias name, or an Alias Node object, may be used as a dependency of any other target, including another alias. alias and source may each be a string or Node object, or a list of strings or Node objects; if Nodes are used for alias they must be Alias nodes. If source is omitted, the alias is created but has no reference; if selected for building this will result in a Nothing to be done. message. An empty alias can be used to define the alias in a visible place in the project; it can later be appended to in a subsidiary SConscript file with the actual target(s) to refer to. The optional action parameter specifies an action or list of actions that will be executed whenever the any of the alias targets are out-of-date. &f-Alias; can be called for an existing alias, which appends the alias and/or action arguments to the existing lists for that alias. Returns a list of Alias Node objects representing the alias(es), which exist outside of any physical file system. The alias name space is separate from the name space for tangible targets; to avoid confusion do not reuse target names as alias names. Examples: Alias('install') Alias('install', '/usr/bin') Alias(['install', 'install-lib'], '/usr/local/lib') env.Alias('install', ['/usr/local/bin', '/usr/local/lib']) env.Alias('install', ['/usr/local/man']) env.Alias('update', ['file1', 'file2'], "update_database $SOURCES")

(target, ...)

Marks each given target so that it is always assumed to be out-of-date, and will always be rebuilt if needed. Note, however, that &f-AlwaysBuild; does not add its target(s) to the default target list, so the targets will only be built if they are specified on the command line, or are a dependent of a target specified on the command line--but they will always be built if so specified. Multiple targets can be passed in to a single call to &f-AlwaysBuild;.

(key=val, [...])

Appends value(s) intelligently to &consvars; in env. The &consvars; and values to add to them are passed as key=val pairs (&Python; keyword arguments). &f-env-Append; is designed to allow adding values without having to think about the data type of an existing &consvar;. Regular &Python; syntax can also be used to manipulate the &consvar;, but for that you may need to know the types involved, for example pure &Python; lets you directly "add" two lists of strings, but adding a string to a list or a list to a string requires different syntax - things &f-Append; takes care of. Some pre-defined &consvars; do have type expectations based on how &SCons; will use them: for example &cv-link-CPPDEFINES; is often a string or a list of strings, but can also be a list of tuples or a dictionary; while &cv-link-LIBEMITTER; is expected to be a callable or list of callables, and &cv-link-BUILDERS; is expected to be a dictionary. Consult the documentation for the various &consvars; for more details. The following descriptions apply to both the &f-Append; and &f-Prepend; methods, as well as their Unique variants, with the differences being the insertion point of the added values and whether duplication is allowed. val can be almost any type. If env does not have a &consvar; named key, then key is simply stored with a value of val. Otherwise, val is combined with the existing value, possibly converting into an appropriate type which can hold the expanded contents. There are a few special cases to be aware of. Normally, when two strings are combined, the result is a new string containing their concatenation (and you are responsible for supplying any needed separation); however, the contents of &cv-link-CPPDEFINES; will be post-processed by adding a prefix and/or suffix to each entry when the command line is produced, so &SCons; keeps them separate - appending a string will result in a separate string entry, not a combined string. For &cv-CPPDEFINES;. as well as &cv-link-LIBS;, and the various *PATH variables, &SCons; will amend the variable by supplying the compiler-specific syntax (e.g. prepending a -D or /D prefix for &cv-CPPDEFINES;), so you should omit this syntax when adding values to these variables. Examples (gcc syntax shown in the expansion of &CPPDEFINES;): env = Environment(CXXFLAGS="-std=c11", CPPDEFINES="RELEASE") print(f"CXXFLAGS = {env['CXXFLAGS']}, CPPDEFINES = {env['CPPDEFINES']}") # notice including a leading space in CXXFLAGS addition env.Append(CXXFLAGS=" -O", CPPDEFINES="EXTRA") print(f"CXXFLAGS = {env['CXXFLAGS']}, CPPDEFINES = {env['CPPDEFINES']}") print("CPPDEFINES will expand to", env.subst('$_CPPDEFFLAGS')) $ scons -Q CXXFLAGS = -std=c11, CPPDEFINES = RELEASE CXXFLAGS = -std=c11 -O, CPPDEFINES = deque(['RELEASE', 'EXTRA']) CPPDEFINES will expand to -DRELEASE -DEXTRA scons: `.' is up to date. Because &cv-link-CPPDEFINES; is intended for command-line specification of C/C++ preprocessor macros, additional syntax is accepted when adding to it. The preprocessor accepts arguments to predefine a macro name by itself (-DFOO for most compilers, /DFOO for Microsoft C++), which gives it an implicit value of 1, or can be given with a replacement value (-DBAR=TEXT). &SCons; follows these rules when adding to &cv-CPPDEFINES;: A string is split on spaces, giving an easy way to enter multiple macros in one addition. Use an = to specify a valued macro. A tuple is treated as a valued macro. Use the value None if the macro should not have a value. It is an error to supply more than two elements in such a tuple. A list is processed in order, adding each item without further interpretation. In this case, space-separated strings are not split. A dictionary is processed in order, adding each key-value pair as a valued macro. Use the value None if the macro should not have a value. Examples: env = Environment(CPPDEFINES="FOO") print("CPPDEFINES =", env['CPPDEFINES']) env.Append(CPPDEFINES="BAR=1") print("CPPDEFINES =", env['CPPDEFINES']) env.Append(CPPDEFINES=[("OTHER", 2)]) print("CPPDEFINES =", env['CPPDEFINES']) env.Append(CPPDEFINES={"EXTRA": "arg"}) print("CPPDEFINES =", env['CPPDEFINES']) print("CPPDEFINES will expand to", env.subst('$_CPPDEFFLAGS')) $ scons -Q CPPDEFINES = FOO CPPDEFINES = deque(['FOO', 'BAR=1']) CPPDEFINES = deque(['FOO', 'BAR=1', ('OTHER', 2)]) CPPDEFINES = deque(['FOO', 'BAR=1', ('OTHER', 2), ('EXTRA', 'arg')]) CPPDEFINES will expand to -DFOO -DBAR=1 -DOTHER=2 -DEXTRA=arg scons: `.' is up to date. Examples of adding multiple macros: env = Environment() env.Append(CPPDEFINES=[("ONE", 1), "TWO", ("THREE", )]) print("CPPDEFINES =", env['CPPDEFINES']) env.Append(CPPDEFINES={"FOUR": 4, "FIVE": None}) print("CPPDEFINES =", env['CPPDEFINES']) print("CPPDEFINES will expand to", env.subst('$_CPPDEFFLAGS')) $ scons -Q CPPDEFINES = [('ONE', 1), 'TWO', ('THREE',)] CPPDEFINES = deque([('ONE', 1), 'TWO', ('THREE',), ('FOUR', 4), ('FIVE', None)]) CPPDEFINES will expand to -DONE=1 -DTWO -DTHREE -DFOUR=4 -DFIVE scons: `.' is up to date. Changed in version 4.5: clarified the use of tuples vs. other types, handling is now consistent across the four functions. env = Environment() env.Append(CPPDEFINES=("MACRO1", "MACRO2")) print("CPPDEFINES =", env['CPPDEFINES']) env.Append(CPPDEFINES=[("MACRO3", "MACRO4")]) print("CPPDEFINES =", env['CPPDEFINES']) print("CPPDEFINES will expand to", env.subst('$_CPPDEFFLAGS')) $ scons -Q CPPDEFINES = ('MACRO1', 'MACRO2') CPPDEFINES = deque(['MACRO1', 'MACRO2', ('MACRO3', 'MACRO4')]) CPPDEFINES will expand to -DMACRO1 -DMACRO2 -DMACRO3=MACRO4 scons: `.' is up to date. See &cv-link-CPPDEFINES; for more details. Appending a string val to a dictionary-typed &consvar; enters val as the key in the dictionary, and None as its value. Using a tuple type to supply a key-value pair only works for the special case of &cv-CPPDEFINES; described above. Although most combinations of types work without needing to know the details, some combinations do not make sense and &Python; raises an exception. When using &f-env-Append; to modify &consvars; which are path specifications (conventionally, the names of such end in PATH), it is recommended to add the values as a list of strings, even if you are only adding a single string. The same goes for adding library names to &cv-LIBS;. env.Append(CPPPATH=["#/include"]) See also &f-link-env-AppendUnique;, &f-link-env-Prepend; and &f-link-env-PrependUnique;.

(name, newpath, [envname, sep, delete_existing=False])

Append path elements specified by newpath to the given search path string or list name in mapping envname in the &consenv;. Supplying envname is optional: the default is the execution environment &cv-link-ENV;. Optional sep is used as the search path separator, the default is the platform's separator (os.pathsep). A path element will only appear once. Any duplicates in newpath are dropped, keeping the last appearing (to preserve path order). If delete_existing is False (the default) any addition duplicating an existing path element is ignored; if delete_existing is True the existing value will be dropped and the path element will be added at the end. To help maintain uniqueness all paths are normalized (using os.path.normpath and os.path.normcase). Example: print('before:', env['ENV']['INCLUDE']) include_path = '/foo/bar:/foo' env.AppendENVPath('INCLUDE', include_path) print('after:', env['ENV']['INCLUDE']) Yields: before: /foo:/biz after: /biz:/foo/bar:/foo See also &f-link-env-PrependENVPath;.

(key=val, [...], [delete_existing=False])

Append values to &consvars; in the current &consenv;, maintaining uniqueness. Works like &f-link-env-Append;, except that values that would become duplicates are not added. If delete_existing is set to a true value, then for any duplicate, the existing instance of val is first removed, then val is appended, having the effect of moving it to the end. Example: env.AppendUnique(CCFLAGS='-g', FOO=['foo.yyy']) See also &f-link-env-Append;, &f-link-env-Prepend; and &f-link-env-PrependUnique;.

(action, [arguments])

Creates a Builder object for the specified action. See the manpage section "Builder Objects" for a complete explanation of the arguments and behavior. Note that the env.Builder() form of the invocation will expand &consvars; in any arguments strings, including the action argument, at the time it is called using the &consvars; in the env &consenv; through which &f-env-Builder; was called. The &f-Builder; form delays all variable expansion until after the Builder object is actually called.

(cache_dir, custom_class=None)

Direct &scons; to maintain a derived-file cache in cache_dir. The derived files in the cache will be shared among all the builds specifying the same cache_dir. Specifying a cache_dir of None disables derived file caching. Calling the environment method &f-link-env-CacheDir; limits the effect to targets built through the specified &consenv;. Calling the global function &f-link-CacheDir; sets a global default that will be used by all targets built through &consenvs; that do not set up environment-specific caching by calling &f-env-CacheDir;. Caching behavior can be configured by passing a specialized cache class as the optional custom_class parameter. This class must be a subclass of SCons.CacheDir.CacheDir. &SCons; will internally invoke the custom class for performing caching operations. If the parameter is omitted or set to None, &SCons; will use the default SCons.CacheDir.CacheDir class. When derived-file caching is being used and &scons; finds a derived file that needs to be rebuilt, it will first look in the cache to see if a file with matching &buildsig; exists (indicating the input file(s) and build action(s) were identical to those for the current target), and if so, will retrieve the file from the cache. &scons; will report Retrieved `file' from cache instead of the normal build message. If the derived file is not present in the cache, &scons; will build it and then place a copy of the built file in the cache, identified by its &buildsig;, for future use. The Retrieved `file' from cache messages are useful for human consumption, but less useful when comparing log files between &scons; runs which will show differences that are noisy and not actually significant. To disable, use the option. With this option, &scons; changes printing to always show the action that would have been used to build the file without caching. Derived-file caching may be disabled for any invocation of &scons; by giving the command line option; cache updating may be disabled, leaving cache fetching enabled, by giving the option. If the option is used, &scons; will place a copy of all derived files into the cache, even if they already existed and were not built by this invocation. This is useful to populate a cache the first time a cache_dir is used for a build, or to bring a cache up to date after a build with cache updating disabled ( or ) has been done. The &f-link-NoCache; method can be used to disable caching of specific files. This can be useful if inputs and/or outputs of some tool are impossible to predict or prohibitively large. Note that (at this time) &SCons; provides no facilities for managing the derived-file cache. It is up to the developer to arrange for cache pruning, expiry, access control, etc. if needed.

(targets, files)

Set additional files for removal when any of targets are selected for cleaning ( command line option). targets and files can each be a single filename or node, or a list of filenames or nodes. These can refer to files or directories. Calling this method repeatedly has an additive effect. The related &f-link-NoClean; method has higher priority: any target specified to &f-NoClean; will not be cleaned even if also given as a files parameter to &f-Clean;. Examples: Clean('foo', ['bar', 'baz']) Clean('dist', env.Program('hello', 'hello.c')) Clean(['foo', 'bar'], 'something_else_to_clean') &SCons; does not directly track directories as targets - they are created if needed and not normally removed in clean mode. In this example, installing the project creates a subdirectory for the documentation. The &f-Clean; call ensures that the subdirectory is removed if the project is uninstalled. Clean(docdir, os.path.join(docdir, projectname))

([key=val, ...])

Returns an independent copy of a &consenv;. If there are any unrecognized keyword arguments specified, they are added as &consvars; in the copy, overwriting any existing values for those keywords. See the manpage section "Construction Environments" for more details. Example: env2 = env.Clone() env3 = env.Clone(CCFLAGS='-g') A list of tools and a toolpath may be specified, as in the &f-link-Environment; constructor: def MyTool(env): env['FOO'] = 'bar' env4 = env.Clone(tools=['msvc', MyTool]) The parse_flags keyword argument is also recognized, to allow merging command-line style arguments into the appropriate construction variables (see &f-link-env-MergeFlags;). # create an environment for compiling programs that use wxWidgets wx_env = env.Clone(parse_flags='!wx-config --cflags --cxxflags') The variables keyword argument is also recognized, to allow (re)initializing &consvars; from a Variables object. Changed in version 4.8.0: the variables parameter was added.

There is actually no Builder named &Command;, rather the term "Command Builder" refers to a function which, on each call, creates and calls an anonymous Builder. This is useful for "one-off" builds where a full Builder is not needed. Since the anonymous Builder is never hooked into the standard Builder framework, an Action must always be specified. See the &f-link-Command; function description for the calling syntax and details.

(target, source, action, [key=val, ...])

Creates an anonymous builder and calls it, thus recording action to build target from source into the dependency tree. This can be more convenient for a single special-case build than having to define and add a new named Builder. The &Command; function accepts the source_scanner and target_scanner keyword arguments which are used to specify custom scanners for the specified sources or targets. The value must be a Scanner object. For example, the global DirScanner object can be used if any of the sources will be directories that must be scanned on-disk for changes to files that aren't already specified in other Builder or function calls. The &Command; function also accepts the source_factory and target_factory keyword arguments which are used to specify factory functions to create &SCons; Nodes from any sources or targets specified as strings. If any sources or targets are already Node objects, they are not further transformed even if a factory is specified for them. The default for each is the &Entry; factory. These four arguments, if given, are used in the creation of the Builder. Other Builder-specific keyword arguments are not recognized as such. See the manpage section "Builder Objects" for more information about how these arguments work in a Builder. Any remaining keyword arguments are passed on to the generated builder when it is called, and behave as described in the manpage section "Builder Methods", in short: recognized arguments have their specified meanings, while the rest are used to override any same-named existing &consvars; from the &consenv;. action can be an external command, specified as a string, or a callable &Python; object; see the manpage section "Action Objects" for more complete information. Also note that a string specifying an external command may be preceded by an at-sign (@) to suppress printing the command in question, or by a hyphen (-) to ignore the exit status of the external command. Examples: env.Command( target='foo.out', source='foo.in', action="$FOO_BUILD < $SOURCES > $TARGET" ) env.Command( target='bar.out', source='bar.in', action=["rm -f $TARGET", "$BAR_BUILD < $SOURCES > $TARGET"], ENV={'PATH': '/usr/local/bin/'}, ) import os def rename(env, target, source): os.rename('.tmp', str(target[0])) env.Command( target='baz.out', source='baz.in', action=["$BAZ_BUILD < $SOURCES > .tmp", rename], ) Note that the &Command; function will usually assume, by default, that the specified targets and/or sources are Files, if no other part of the configuration identifies what type of entries they are. If necessary, you can explicitly specify that targets or source nodes should be treated as directories by using the &f-link-Dir; or &f-link-env-Dir; functions. Examples: env.Command('ddd.list', Dir('ddd'), 'ls -l $SOURCE > $TARGET') env['DISTDIR'] = 'destination/directory' env.Command(env.Dir('$DISTDIR')), None, make_distdir) Also note that SCons will usually automatically create any directory necessary to hold a target file, so you normally don't need to create directories by hand.

(env, [custom_tests, conf_dir, log_file, config_h]) ([custom_tests, conf_dir, log_file, config_h])

Creates a &Configure; object for integrated functionality similar to GNU autoconf. See the manpage section "Configure Contexts" for a complete explanation of the arguments and behavior.

(function)

Specifies that all up-to-date decisions for targets built through this &consenv; will be handled by function. function can be the name of a function or one of the following strings that specify a predefined decider function: "content" Specifies that a target shall be considered out-of-date and rebuilt if the dependency's content has changed since the last time the target was built, as determined by performing a checksum on the dependency's contents using the selected hash function, and comparing it to the checksum recorded the last time the target was built. content is the default decider. Changed in version 4.1: The decider was renamed to content since the hash function is now selectable. The former name, MD5, can still be used as a synonym, but is deprecated. "content-timestamp" Specifies that a target shall be considered out-of-date and rebuilt if the dependency's content has changed since the last time the target was built, except that dependencies with a timestamp that matches the last time the target was rebuilt will be assumed to be up-to-date and not rebuilt. This provides behavior very similar to the content behavior of always checksumming file contents, with an optimization of not checking the contents of files whose timestamps haven't changed. The drawback is that SCons will not detect if a file's content has changed but its timestamp is the same, as might happen in an automated script that runs a build, updates a file, and runs the build again, all within a single second. Changed in version 4.1: The decider was renamed to content-timestamp since the hash function is now selectable. The former name, MD5-timestamp, can still be used as a synonym, but is deprecated. "timestamp-newer" Specifies that a target shall be considered out-of-date and rebuilt if the dependency's timestamp is newer than the target file's timestamp. This is the behavior of the classic Make utility, and make can be used a synonym for timestamp-newer. "timestamp-match" Specifies that a target shall be considered out-of-date and rebuilt if the dependency's timestamp is different than the timestamp recorded the last time the target was built. This provides behavior very similar to the classic Make utility (in particular, files are not opened up so that their contents can be checksummed) except that the target will also be rebuilt if a dependency file has been restored to a version with an earlier timestamp, such as can happen when restoring files from backup archives. Examples: # Use exact timestamp matches by default. Decider('timestamp-match') # Use hash content signatures for any targets built # with the attached &consenv;. env.Decider('content') In addition to the above already-available functions, the function argument may be a &Python; function you supply. Such a function must accept the following four arguments: dependency The Node (file) which should cause the target to be rebuilt if it has "changed" since the last time target was built. target The Node (file) being built. In the normal case, this is what should get rebuilt if the dependency has "changed." prev_ni Stored information about the state of the dependency the last time the target was built. This can be consulted to match various file characteristics such as the timestamp, size, or &contentsig;. repo_node If set, use this Node instead of the one specified by dependency to determine if the dependency has changed. This argument is optional so should be written as a default argument (typically it would be written as repo_node=None). A caller will normally only set this if the target only exists in a Repository. The function should return a value which evaluates True if the dependency has "changed" since the last time the target was built (indicating that the target should be rebuilt), and a value which evaluates False otherwise (indicating that the target should not be rebuilt). Note that the decision can be made using whatever criteria are appropriate. Ignoring some or all of the function arguments is perfectly normal. Example: def my_decider(dependency, target, prev_ni, repo_node=None): return not os.path.exists(str(target)) env.Decider(my_decider)

(target, dependency)

Specifies an explicit dependency; the target will be rebuilt whenever the dependency has changed. Both the specified target and dependency can be a string (usually the path name of a file or directory) or Node objects, or a list of strings or Node objects (such as returned by a Builder call). This should only be necessary for cases where the dependency is not caught by a Scanner for the file. Example: env.Depends('foo', 'other-input-file-for-foo') mylib = env.Library('mylib.c') installed_lib = env.Install('lib', mylib) bar = env.Program('bar.c') # Arrange for the library to be copied into the installation # directory before trying to build the "bar" program. # (Note that this is for example only. A "real" library # dependency would normally be configured through the $LIBS # and $LIBPATH variables, not using an env.Depends() call.) env.Depends(bar, installed_lib)

(progs)

Find an executable from one or more choices: progs may be a string or a list of strings. Returns the first value from progs that was found, or None. Executable is searched by checking the paths in the execution environment (env['ENV']['PATH']). On Windows systems, additionally applies the filename suffixes found in the execution environment (env['ENV']['PATHEXT']) but will not include any such extension in the return value. &f-env-Detect; is a wrapper around &f-link-env-WhereIs;.

([var, ...], [as_dict=])

Return an object containing &consvars; from env. If var is omitted, all the &consvars; with their values are returned in a dict. If var is specified, and as_dict is true, the specified &consvars; are returned in a dict; otherwise (the default, for backwards compatibility), values only are returned, as a scalar if one var is given, or as a list if multiples. Example: cvars = env.Dictionary() cc_values = env.Dictionary('CC', 'CCFLAGS', 'CCCOM') The object returned by &f-link-env-Dictionary; should be treated as a read-only view into the &consvars;. Some &consvars; require special internal handling, and modifying them through the &f-env-Dictionary; object can bypass that handling and cause data inconsistencies. The primary use of &f-env-Dictionary; is for diagnostic purposes - it is used widely by test cases specifically because it bypasses the special handling so that behavior can be verified. Changed in 4.9.0: as_dict added.

(name, [directory])

Returns Directory Node(s). A Directory Node is an object that represents a directory. name can be a relative or absolute path or a list of such paths. directory is an optional directory that will be used as the parent directory. If no directory is specified, the current script's directory is used as the parent. If name is a single pathname, the corresponding node is returned. If name is a list, SCons returns a list of nodes. Construction variables are expanded in name. Directory Nodes can be used anywhere you would supply a string as a directory name to a Builder method or function. Directory Nodes have attributes and methods that are useful in many situations; see manpage section "Filesystem Nodes" for more information.

([var, ...], [format=TYPE])

Serialize &consvars; from env to a string. If var is omitted, all the &consvars; are serialized. If one or more var values are supplied, only those variables and their values are serialized. The optional format string selects the serialization format: pretty Returns a pretty-printed representation of the &consvars; - the result will look like a &Python; dict (this is the default). json Returns a JSON-formatted representation of the variables. The variables will be presented as a JSON object literal, the JSON equivalent of a &Python; dict.. Changed in 4.9.0: More than one key can be specified. The returned string always looks like a dict (or equivalent in other formats); previously a single key serialized only the value, not the key with the value. Examples: this &SConstruct; env = Environment() print(env.Dump('CCCOM')) print(env.Dump('CC', 'CCFLAGS', format='json')) will print something like: {'CCCOM': '$CC -o $TARGET -c $CFLAGS $CCFLAGS $_CCCOMCOM $SOURCES'} { "CC": "gcc", "CCFLAGS": [] } While this &SConstruct;: env = Environment() print(env.Dump()) will print something like: { 'AR': 'ar', 'ARCOM': '$AR $ARFLAGS $TARGET $SOURCES\n$RANLIB $RANLIBFLAGS $TARGET', 'ARFLAGS': ['r'], 'AS': 'as', 'ASCOM': '$AS $ASFLAGS -o $TARGET $SOURCES', 'ASFLAGS': [], ...

([key=value, ...])

Return a new &consenv; initialized with the specified key=value pairs. The keyword arguments parse_flags, platform, toolpath, tools and variables are specially recognized and do not lead to &consvar; creation. See the manpage section "Construction Environments" for more details.

(action, [actionargs ...])

Executes an Action. action may be an Action object or it may be a command-line string, list of commands, or executable &Python; function, each of which will first be converted into an Action object and then executed. Any additional arguments to &f-Execute; are passed on to the &f-link-Action; factory function which actually creates the Action object (see the manpage section Action Objects for a description). Example: Execute(Copy('file.out', 'file.in')) &f-Execute; performs its action immediately, as part of the SConscript-reading phase. There are no sources or targets declared in an &f-Execute; call, so any objects it manipulates will not be tracked as part of the &SCons; dependency graph. In the example above, neither file.out nor file.in will be tracked objects. &f-Execute; returns the exit value of the command or return value of the &Python; function. &scons; prints an error message if the executed action fails (exits with or returns a non-zero value), however it does not, automatically terminate the build for such a failure. If you want the build to stop in response to a failed &f-Execute; call, you must explicitly check for a non-zero return value: if Execute("mkdir sub/dir/ectory"): # The mkdir failed, don't try to build. Exit(1)

(name, [directory])

Returns File Node(s). A File Node is an object that represents a file. name can be a relative or absolute path or a list of such paths. directory is an optional directory that will be used as the parent directory. If no directory is specified, the current script's directory is used as the parent. If name is a single pathname, the corresponding node is returned. If name is a list, SCons returns a list of nodes. Construction variables are expanded in name. File Nodes can be used anywhere you would supply a string as a file name to a Builder method or function. File Nodes have attributes and methods that are useful in many situations; see manpage section "Filesystem Nodes" for more information.

(file, dirs)

Search for file in the path specified by dirs. dirs may be a list of directory names or a single directory name. In addition to searching for files that exist in the filesystem, this function also searches for derived files that have not yet been built. Example: foo = env.FindFile('foo', ['dir1', 'dir2'])

()

Returns the list of targets set up by the &b-link-Install; or &b-link-InstallAs; builders. This function serves as a convenient method to select the contents of a binary package. Example: Install('/bin', ['executable_a', 'executable_b']) # will return the file node list # ['/bin/executable_a', '/bin/executable_b'] FindInstalledFiles() Install('/lib', ['some_library']) # will return the file node list # ['/bin/executable_a', '/bin/executable_b', '/lib/some_library'] FindInstalledFiles()

(node='"."')

Returns the list of nodes which serve as the source of the built files. It does so by inspecting the dependency tree starting at the optional argument node which defaults to the '"."'-node. It will then return all leaves of node. These are all children which have no further children. This function is a convenient method to select the contents of a Source Package. Example: Program('src/main_a.c') Program('src/main_b.c') Program('main_c.c') # returns ['main_c.c', 'src/main_a.c', 'SConstruct', 'src/main_b.c'] FindSourceFiles() # returns ['src/main_b.c', 'src/main_a.c' ] FindSourceFiles('src') As you can see, build support files (&SConstruct; in the above example) will also be returned by this function.

(sequence)

Takes a sequence (that is, a &Python; list or tuple) that may contain nested sequences and returns a flattened list containing all of the individual elements in any sequence. This can be helpful for collecting the lists returned by calls to Builders; other Builders will automatically flatten lists specified as input, but direct &Python; manipulation of these lists does not. Examples: foo = Object('foo.c') bar = Object('bar.c') # Because `foo' and `bar' are lists returned by the Object() Builder, # `objects' will be a list containing nested lists: objects = ['f1.o', foo, 'f2.o', bar, 'f3.o'] # Passing such a list to another Builder is all right because # the Builder will flatten the list automatically: Program(source = objects) # If you need to manipulate the list directly using &Python;, you need to # call Flatten() yourself, or otherwise handle nested lists: for object in Flatten(objects): print(str(object))

(file, [...])

Returns the &scons; path name (or names) for the specified file (or files). The specified file or files may be &scons; Nodes or strings representing path names.

(pattern, [ondisk=True, source=False, strings=False, exclude=None])

Returns a possibly empty list of Nodes (or strings) that match pathname specification pattern. pattern can be absolute, top-relative, or (most commonly) relative to the directory of the current &SConscript; file. &f-Glob; matches both files stored on disk and Nodes which &SCons; already knows about, even if any corresponding file is not currently stored on disk. The environment method form (&f-env-Glob;) performs string substitution on pattern and returns whatever matches the resulting expanded pattern. The results are sorted, unlike for the similar &Python; glob.glob function, to ensure build order will be stable. pattern can contain POSIX-style shell metacharacters for matching: Pattern Meaning * matches everything ? matches any single character [seq] matches any character in seq (can be a list or a range). [!seq] matches any character not in seq For a literal match, wrap the metacharacter in brackets to escape the normal behavior. For example, '[?]' matches the character '?'. Filenames starting with a dot are specially handled - they can only be matched by patterns that start with a dot (or have a dot immediately following a pathname separator character, or slash), they are not not matched by the metacharacters. Metacharacter matches also do not span directory separators. &f-Glob; understands repositories (see the &f-link-Repository; function) and source directories (see the &f-link-VariantDir; function) and returns a Node (or string, if so configured) match in the local (SConscript) directory if a matching Node is found anywhere in a corresponding repository or source directory. If the optional ondisk argument evaluates false, the search for matches on disk is disabled, and only matches from already-configured File or Dir Nodes are returned. The default is to return Nodes for matches on disk as well. If the optional source argument evaluates true, and the local directory is a variant directory, then &f-Glob; returns Nodes from the corresponding source directory, rather than the local directory. If the optional strings argument evaluates true, &f-Glob; returns matches as strings, rather than Nodes. The returned strings will be relative to the local (SConscript) directory. (Note that while this may make it easier to perform arbitrary manipulation of file names, it loses the context &SCons; would have in the Node, so if the returned strings are passed to a different &SConscript; file, any Node translation there will be relative to that &SConscript; directory, not to the original &SConscript; directory.) The optional exclude argument may be set to a pattern or a list of patterns describing files or directories to filter out of the match list. Elements matching a least one specified pattern will be excluded. These patterns use the same syntax as for pattern. Examples: Program("foo", Glob("*.c")) Zip("/tmp/everything", Glob(".??*") + Glob("*")) sources = Glob("*.cpp", exclude=["os_*_specific_*.cpp"]) \ + Glob("os_%s_specific_*.cpp" % currentOS)

(target, dependency)

Ignores dependency when deciding if target needs to be rebuilt. target and dependency can each be a single filename or Node or a list of filenames or Nodes. &f-Ignore; can also be used to remove a target from the default build by specifying the directory the target will be built in as target and the file you want to skip selecting for building as dependency. Note that this only removes the target from the default target selection algorithm: if it is a dependency of another object being built &SCons; still builds it normally. See the third and forth examples below. Examples: env.Ignore('foo', 'foo.c') env.Ignore('bar', ['bar1.h', 'bar2.h']) env.Ignore('.', 'foobar.obj') env.Ignore('bar', 'bar/foobar.obj')

(string)

The specified string will be preserved as-is and not have &consvars; expanded.

(targets)

The specified targets will have copies made in the local tree, even if an already up-to-date copy exists in a repository. Returns a list of the target Node or Nodes.

(arg, [unique])

Merges values from arg into &consvars; in env. If arg is a dictionary, each key-value pair represents a &consvar; name and the corresponding flags to merge. If arg is not a dictionary, &MergeFlags; attempts to convert it to one before the values are merged. &f-link-env-ParseFlags; is used for this, so values to be converted are subject to the same limitations: &ParseFlags; has knowledge of which &consvars; certain flags should go to, but not all; and only for GCC and compatible compiler chains. arg must be a single object, so to pass multiple strings, enclose them in a list. If unique is true (the default), duplicate values are not retained. In case of duplication, any &consvar; names that end in PATH keep the left-most value so the path search order is not altered. All other &consvars; keep the right-most value. If unique is false, values are appended even if they are duplicates. Examples: # Add an optimization flag to $CCFLAGS. env.MergeFlags({'CCFLAGS': '-O3'}) # Combine the flags returned from running pkg-config with an optimization # flag and merge the result into the construction variables. env.MergeFlags(['!pkg-config gtk+-2.0 --cflags', '-O3']) # Combine an optimization flag with the flags returned from running pkg-config # for two distinct packages and merge into the construction variables. env.MergeFlags( [ '-O3', '!pkg-config gtk+-2.0 --cflags --libs', '!pkg-config libpng12 --cflags --libs', ] )

(target, ...)

Specifies a list of files which should not be cached whenever the &f-link-CacheDir; method has been activated. The specified targets may be a list or an individual target. Multiple files should be specified either as separate arguments to the &f-NoCache; method, or as a list. &f-NoCache; will also accept the return value of any of the &consenv; Builder methods. Calling &f-NoCache; on directories and other non-File Node types has no effect because only File Nodes are cached. Examples: NoCache('foo.elf') NoCache(env.Program('hello', 'hello.c'))

(targets, ...)

Specifies files or directories which should not be removed whenever a specified target (or its dependencies) is selected and clean mode is active ( command line option). targets may be one or more file or directory names or nodes, and/or lists of names or nodes. &f-NoClean; can be called multiple times. Calling &f-NoClean; for a target overrides calling &f-link-Clean; for the same target, so any targets passed to both functions will not be removed in clean mode. Examples: NoClean('foo.elf') NoClean(env.Program('hello', 'hello.c'))

(command, [function, unique])

Updates the current &consenv; with the values extracted from the output of running external command, by passing it to a helper function. command may be a string or a list of strings representing the command and its arguments. If function is omitted or None, &f-link-env-MergeFlags; is used. By default, duplicate values are not added to any &consvars;; you can specify unique=False to allow duplicate values to be added. command is executed using the SCons execution environment (that is, the &consvar; &cv-link-ENV; in the current &consenv;). If command needs additional information to operate properly, that needs to be set in the execution environment. For example, pkg-config may need a custom value set in the PKG_CONFIG_PATH environment variable. &f-env-MergeFlags; needs to understand the output produced by command in order to distribute it to appropriate &consvars;. &f-env-MergeFlags; uses a separate function to do that processing - see &f-link-env-ParseFlags; for the details, including a table of options and corresponding &consvars;. To provide alternative processing of the output of command, you can supply a custom function, which must accept three arguments: the &consenv; to modify, a string argument containing the output from running command, and the optional unique flag.

(filename, [must_exist, only_one])

Parses the contents of filename as a list of dependencies in the style of &Make; or mkdep, and explicitly establishes all of the listed dependencies. By default, it is not an error if filename does not exist. The optional must_exist argument may be set to True to have &SCons; raise an exception if the file does not exist, or is otherwise inaccessible. The optional only_one argument may be set to True to have &SCons; raise an exception if the file contains dependency information for more than one target. This can provide a small sanity check for files intended to be generated by, for example, the gcc -M flag, which should typically only write dependency information for one output file into a corresponding .d file. filename and all of the files listed therein will be interpreted relative to the directory of the &SConscript; file which calls the &f-ParseDepends; function.

(flags, ...)

Parses one or more strings containing typical command-line flags for GCC-style tool chains and returns a dictionary with the flag values separated into the appropriate SCons &consvars;. Intended as a companion to the &f-link-env-MergeFlags; method, but allows for the values in the returned dictionary to be modified, if necessary, before merging them into the &consenv;. (Note that &f-env-MergeFlags; will call this method if its argument is not a dictionary, so it is usually not necessary to call &f-env-ParseFlags; directly unless you want to manipulate the values.) If the first character in any string is an exclamation mark (!), the rest of the string is executed as a command, and the output from the command is parsed as GCC tool chain command-line flags and added to the resulting dictionary. This can be used to call a *-config command typical of the POSIX programming environment (for example, pkg-config). Note that such a command is executed using the SCons execution environment; if the command needs additional information, that information needs to be explicitly provided. See &f-link-ParseConfig; for more details. Flag values are translated according to the prefix found, and added to the following &consvars;: -arch CCFLAGS, LINKFLAGS -D CPPDEFINES -framework FRAMEWORKS -frameworkdir= FRAMEWORKPATH -fmerge-all-constants CCFLAGS, LINKFLAGS -fopenmp CCFLAGS, LINKFLAGS -fsanitize CCFLAGS, LINKFLAGS -include CCFLAGS -imacros CCFLAGS -isysroot CCFLAGS, LINKFLAGS -isystem CCFLAGS -iquote CCFLAGS -idirafter CCFLAGS -I CPPPATH -l LIBS -L LIBPATH -mno-cygwin CCFLAGS, LINKFLAGS -mwindows LINKFLAGS -openmp CCFLAGS, LINKFLAGS -pthread CCFLAGS, LINKFLAGS -std= CFLAGS -stdlib= CXXFLAGS -Wa, ASFLAGS, CCFLAGS -Wl,-rpath= RPATH -Wl,-R, RPATH -Wl,-R RPATH -Wl, LINKFLAGS -Wp, CPPFLAGS - CCFLAGS + CCFLAGS, LINKFLAGS Any other strings not associated with options are assumed to be the names of libraries and added to the &cv-LIBS; &consvar;. Examples (all of which produce the same result): dict = env.ParseFlags('-O2 -Dfoo -Dbar=1') dict = env.ParseFlags('-O2', '-Dfoo', '-Dbar=1') dict = env.ParseFlags(['-O2', '-Dfoo -Dbar=1']) dict = env.ParseFlags('-O2', '!echo -Dfoo -Dbar=1')

(plat) (plat)

When called as a global function, returns a callable platform object selected by plat (defaults to the detected platform for the current system) that can be used to initialize a &consenv; by passing it as the platform keyword argument to the &f-link-Environment; function. Example: env = Environment(platform=Platform('win32')) When called as a method of an environment, calls the platform object indicated by plat to update that environment. env.Platform('posix') See the manpage section "Construction Environments" for more details.

(key=val, [...])

Prepend values to &consvars; in the current &consenv;, works like &f-link-env-Append; (see for details), except that values are added to the front, rather than the end, of any existing value of the &consvar; Example: env.Prepend(CCFLAGS='-g ', FOO=['foo.yyy']) See also &f-link-env-Append;, &f-link-env-AppendUnique; and &f-link-env-PrependUnique;.

(name, newpath, [envname, sep, delete_existing=True])

Prepend path elements specified by newpath to the given search path string or list name in mapping envname in the &consenv;. Supplying envname is optional: the default is the execution environment &cv-link-ENV;. Optional sep is used as the search path separator, the default is the platform's separator (os.pathsep). A path element will only appear once. Any duplicates in newpath are dropped, keeping the first appearing (to preserve path order). If delete_existing is False any addition duplicating an existing path element is ignored; if delete_existing is True (the default) the existing value will be dropped and the path element will be inserted at the beginning. To help maintain uniqueness all paths are normalized (using os.path.normpath and os.path.normcase). Example: print('before:', env['ENV']['INCLUDE']) include_path = '/foo/bar:/foo' env.PrependENVPath('INCLUDE', include_path) print('after:', env['ENV']['INCLUDE']) Yields: before: /biz:/foo after: /foo/bar:/foo:/biz See also &f-link-env-AppendENVPath;.

(key=val, [...], [delete_existing=False])

Prepend values to &consvars; in the current &consenv;, maintaining uniqueness. Works like &f-link-env-Append;, except that values are added to the front, rather than the end, of the &consvar;, and values that would become duplicates are not added. If delete_existing is set to a true value, then for any duplicate, the existing instance of val is first removed, then val is inserted, having the effect of moving it to the front. Example: env.PrependUnique(CCFLAGS='-g', FOO=['foo.yyy']) See also &f-link-env-Append;, &f-link-env-AppendUnique; and &f-link-env-Prepend;.

(modulename)

Finds the location of modulename, which can be a string or a sequence of strings, each representing the name of a &Python; module. Construction variables are expanded in modulename. Returns a Directory Node (see &f-link-Dir;), or a list of Directory Nodes if modulename is a sequence. None is returned for any module not found. When a Tool module which is installed as a &Python; module is used, you need to specify a toolpath argument to &f-link-Tool;, &f-link-Environment; or &f-link-Clone;, as tools outside the standard project locations (site_scons/site_tools) will not be found otherwise. Using &f-PyPackageDir; allows this path to be discovered at runtime instead of hardcoding the path. Example: env = Environment( tools=["default", "ExampleTool"], toolpath=[PyPackageDir("example_tool")] )

(key=val, [...])

Replaces &consvars; in the Environment with the specified keyword arguments. Example: env.Replace(CCFLAGS='-g', FOO='foo.xxx')

(directory)

Sets directory as a repository to be searched for files contributing to the build. Multiple calls to &f-Repository; are allowed, with repositories searched in the given order. Repositories specified via command-line option have higher priority. In &scons;, a repository is partial or complete copy of the source tree, from the top-level directory down, containing source files that can be used to build targets in the current worktree. Repositories can also contain derived files. An example might be an official source tree maintained by an integrator. If a repository contains derived files, they should be the result of building with &SCons;, so a signature database (sconsign) is present in the repository, allowing better decisions on whether they are up-to-date or not. Note that if an up-to-date derived file already exists in a repository, &scons; will not make a copy in the local directory tree. If you need a local copy to be made, use the &f-link-Local; method.

(target, prerequisite)

Specifies an order-only relationship between target and prerequisite. The prerequisites will be (re)built, if necessary, before the target file(s), but the target file(s) do not actually depend on the prerequisites and will not be rebuilt simply because the prerequisite file(s) change. target and prerequisite may each be a string or Node, or a list of strings or Nodes. If there are multiple target values, the prerequisite(s) are added to each one. Returns a list of the affected target nodes. Example: env.Requires('foo', 'file-that-must-be-built-before-foo')

(function, [name, argument, skeys, path_function, node_class, node_factory, scan_check, recursive])

Creates a Scanner object for the specified function. See manpage section "Scanner Objects" for a complete explanation of the arguments and behavior.

(value)

By default, &scons; changes its working directory to the directory in which each subsidiary SConscript file lives while reading and processing that script. This behavior may be disabled by specifying an argument which evaluates false, in which case &scons; will stay in the top-level directory while reading all SConscript files. (This may be necessary when building from repositories, when all the directories in which SConscript files may be found don't necessarily exist locally.) You may enable and disable this ability by calling &f-SConscriptChdir; multiple times. Example: SConscriptChdir(False) SConscript('foo/SConscript') # will not chdir to foo SConscriptChdir(True) SConscript('bar/SConscript') # will chdir to bar

([name, dbm_module])

Specify where to store the &SCons; file signature database, and which database format to use. This may be useful to specify alternate database files and/or file locations for different types of builds. The optional name argument is the base name of the database file(s). If not an absolute path name, these are placed relative to the directory containing the top-level &SConstruct; file. The default is .sconsign. The actual database file(s) stored on disk may have an appropriate suffix appended by the chosen dbm_module The optional dbm_module argument specifies which &Python; database module to use for reading/writing the file. The module must be imported first; then the imported module name is passed as the argument. The default is a custom SCons.dblite module that uses pickled &Python; data structures, which works on all &Python; versions. See documentation of the &Python; dbm module for other available types. If called with no arguments, the database will default to .sconsign.dblite in the top directory of the project, which is also the default if if &f-SConsignFile; is not called. The setting is global, so the only difference between the global function and the environment method form is variable expansion on name. There should only be one active call to this function/method in a given build setup. If name is set to None, &scons; will store file signatures in a separate .sconsign file in each directory, not in a single combined database file. This is a backwards-compatibility measure to support what was the default behavior prior to &SCons; 0.97 (i.e. before 2008). Use of this mode is discouraged and may be deprecated in a future &SCons; release. Examples: # Explicitly stores signatures in ".sconsign.dblite" # in the top-level SConstruct directory (the default behavior). SConsignFile() # Stores signatures in the file "etc/scons-signatures" # relative to the top-level SConstruct directory. # SCons will add a database suffix to this name. SConsignFile("etc/scons-signatures") # Stores signatures in the specified absolute file name. # SCons will add a database suffix to this name. SConsignFile("/home/me/SCons/signatures") # Stores signatures in a separate .sconsign file # in each directory. SConsignFile(None) # Stores signatures in a GNU dbm format .sconsign file import dbm.gnu SConsignFile(dbm_module=dbm.gnu)

(key=val, [...])

Sets &consvars; to default values specified with the keyword arguments if (and only if) the variables are not already set. The following statements are equivalent: env.SetDefault(FOO='foo') if 'FOO' not in env: env['FOO'] = 'foo'

(side_effect, target)

Declares side_effect as a side effect of building target. Both side_effect and target can be a list, a file name, or a node. A side effect is a target file that is created or updated as a side effect of building other targets. For example, a Windows PDB file is created as a side effect of building the .obj files for a static library, and various log files are created updated as side effects of various TeX commands. If a target is a side effect of multiple build commands, &scons; will ensure that only one set of commands is executed at a time. Consequently, you only need to use this method for side-effect targets that are built as a result of multiple build commands. Because multiple build commands may update the same side effect file, by default the side_effect target is not automatically removed when the target is removed by the option. (Note, however, that the side_effect might be removed as part of cleaning the directory in which it lives.) If you want to make sure the side_effect is cleaned whenever a specific target is cleaned, you must specify this explicitly with the &f-link-Clean; or &f-env-Clean; function. This function returns the list of side effect Node objects that were successfully added. If the list of side effects contained any side effects that had already been added, they are not added and included in the returned list.

(arg)

If arg is a string, splits on whitespace and returns a list of strings without whitespace. This mode is the most common case, and can be used to split a list of filenames (for example) rather than having to type them as a list of individually quoted words. If arg is a list or tuple returns the list or tuple unchanged. If arg is any other type of object, returns a list containing just the object. These non-string cases do not actually do any spliting, but allow an argument variable to be passed to &f-Split; without having to first check its type. Example: files = Split("f1.c f2.c f3.c") files = env.Split("f4.c f5.c f6.c") files = Split(""" f7.c f8.c f9.c """)

(input, [raw, target, source, conv])

Performs &consvar; interpolation (substitution) on input, which can be a string or a sequence. Substitutable elements take the form ${expression}, although if there is no ambiguity in recognizing the element, the braces can be omitted. A literal $ can be entered by using $$. By default, leading or trailing white space will be removed from the result, and all sequences of white space will be compressed to a single space character. Additionally, any $( and $) character sequences will be stripped from the returned string, The optional raw argument may be set to 1 if you want to preserve white space and $(-$) sequences. The raw argument may be set to 2 if you want to additionally discard all characters between any $( and $) pairs (as is done for signature calculation). If input is a sequence (list or tuple), the individual elements of the sequence will be expanded, and the results will be returned as a list. The optional target and source keyword arguments must be set to lists of target and source nodes, respectively, if you want the &cv-TARGET;, &cv-TARGETS;, &cv-SOURCE; and &cv-SOURCES; to be available for expansion. This is usually necessary if you are calling &f-env-subst; from within a &Python; function used as an SCons action. Returned string values or sequence elements are converted to their string representation by default. The optional conv argument may specify a conversion function that will be used in place of the default. For example, if you want &Python; objects (including SCons Nodes) to be returned as &Python; objects, you can use a &Python; lambda expression to pass in an unnamed function that simply returns its unconverted argument. Example: print(env.subst("The C compiler is: $CC")) def compile(target, source, env): sourceDir = env.subst( "${SOURCE.srcdir}", target=target, source=source ) source_nodes = env.subst('$EXPAND_TO_NODELIST', conv=lambda x: x)

(name, [toolpath, key=value, ...])

Locates the tool specification module name and returns a callable tool object for that tool. When the environment method (&f-env-Tool;) form is used, the tool object is automatically called before the method returns to update env, and name is appended to the &cv-link-TOOLS; &consvar; in that environment. When the global function &f-Tool; form is used, the tool object is constructed but not called, as it lacks the context of an environment to update, and the returned object needs to be used to arrange for the call. The tool module is searched for in the tool search paths (see the Tools section in the manual page for details) and in any paths specified by the optional toolpath parameter, which must be a list of strings. If toolpath is omitted, the toolpath supplied when the environment was created, if any, is used. Any remaining keyword arguments are saved in the tool object, and will be passed to the tool module's generate function when the tool object is actually called. The generate function can update the &consenv; with &consvars; and arrange any other initialization needed to use the mechanisms that tool describes, and can use these extra arguments to help guide its actions. Changed in version 4.2: &f-env-Tool; now returns the tool object, previously it did not return (i.e. returned None). Examples: env.Tool('gcc') env.Tool('opengl', toolpath=['build/tools']) The returned tool object can be passed to an &f-link-Environment; or &f-link-Clone; call as part of the tools keyword argument, in which case the tool is applied to the environment being constructed, or it can be called directly, in which case a &consenv; to update must be passed as the argument. Either approach will also update the &cv-TOOLS; &consvar;. Examples: env = Environment(tools=[Tool('msvc')]) env = Environment() msvctool = Tool('msvc') msvctool(env) # adds 'msvc' to the TOOLS variable gltool = Tool('opengl', toolpath = ['tools']) gltool(env) # adds 'opengl' to the TOOLS variable

(value, [built_value], [name])

Returns a Node object representing the specified &Python; value. Value Nodes can be used as dependencies of targets. If the string representation of the Value Node changes between &SCons; runs, it is considered out-of-date and any targets depending on it will be rebuilt. Since Value Nodes have no filesystem representation, timestamps are not used; the timestamp deciders perform the same content-based up to date check. The optional built_value argument can be specified when the Value Node is created to indicate the Node should already be considered "built." The optional name parameter can be provided as an alternative name for the resulting Value node; this is advised if the value parameter cannot be converted to a string. Value Nodes have a write method that can be used to "build" a Value Node by setting a new value. The corresponding read method returns the built value of the Node. Changed in version 4.0: the name parameter was added. Examples: env = Environment() def create(target, source, env): """Action function to create a file from a Value. Writes 'prefix=$SOURCE' into the file name given as $TARGET. """ with open(str(target[0]), 'wb') as f: f.write(b'prefix=' + source[0].get_contents() + b'\n') # Fetch the prefix= argument, if any, from the command line. # Use /usr/local as the default. prefix = ARGUMENTS.get('prefix', '/usr/local') # Attach builder named Config to the construction environment # using the 'create' action function above. env['BUILDERS']['Config'] = Builder(action=create) env.Config(target='package-config', source=Value(prefix)) def build_value(target, source, env): """Action function to "build" a Value. Writes contents of $SOURCE into $TARGET, thus updating if it existed. """ target[0].write(source[0].get_contents()) output = env.Value('before') input = env.Value('after') # Attach a builder named UpdateValue to the construction environment # using the 'build_value' action function above. env['BUILDERS']['UpdateValue'] = Builder(action=build_value) env.UpdateValue(target=Value(output), source=Value(input))

(variant_dir, src_dir, [duplicate])

Sets up a mapping to define a variant build directory in variant_dir. src_dir must not be underneath variant_dir. A &f-VariantDir; mapping is global, even if called using the &f-env-VariantDir; form. &f-VariantDir; can be called multiple times with the same src_dir to set up multiple variant builds with different options. Note if variant_dir is not under the project top directory, target selection rules will not pick targets in the variant directory unless they are explicitly specified. When files in variant_dir are referenced, &SCons; backfills as needed with files from src_dir to create a complete build directory. By default, &SCons; physically duplicates the source files, SConscript files, and directory structure as needed into the variant directory. Thus, a build performed in the variant directory is guaranteed to be identical to a build performed in the source directory even if intermediate source files are generated during the build, or if preprocessors or other scanners search for included files using paths relative to the source file, or if individual compilers or other invoked tools are hard-coded to put derived files in the same directory as source files. Only the files &SCons; calculates are needed for the build are duplicated into variant_dir. If possible on the platform, the duplication is performed by linking rather than copying. This behavior is affected by the command-line option. Duplicating the source files may be disabled by setting the duplicate argument to False. This will cause &SCons; to invoke Builders using the path names of source files in src_dir and the path names of derived files within variant_dir. This is more efficient than duplicating, and is safe for most builds; revert to duplicate=True if it causes problems. &f-VariantDir; works most naturally when used with a subsidiary SConscript file. The subsidiary SConscript file must be called as if it were in variant_dir, regardless of the value of duplicate. When calling an SConscript file, you can use the exports keyword argument to pass parameters (individually or as an appropriately set up environment) so the SConscript can pick up the right settings for that variant build. The SConscript must &f-link-Import; these to use them. Example: env1 = Environment(...settings for variant1...) env2 = Environment(...settings for variant2...) # run src/SConscript in two variant directories VariantDir('build/variant1', 'src') SConscript('build/variant1/SConscript', exports={"env": env1}) VariantDir('build/variant2', 'src') SConscript('build/variant2/SConscript', exports={"env": env2}) See also the &f-link-SConscript; function for another way to specify a variant directory in conjunction with calling a subsidiary SConscript file. More examples: # use names in the build directory, not the source directory VariantDir('build', 'src', duplicate=0) Program('build/prog', 'build/source.c') # this builds both the source and docs in a separate subtree VariantDir('build', '.', duplicate=0) SConscript(dirs=['build/src','build/doc']) # same as previous example, but only uses SConscript SConscript(dirs='src', variant_dir='build/src', duplicate=0) SConscript(dirs='doc', variant_dir='build/doc', duplicate=0)

(program, [path, pathext, reject])

Searches for the specified executable program, returning the full path to the program or None. When called as a &consenv; method, searches the paths in the path keyword argument, or if None (the default) the paths listed in the &consenv; (env['ENV']['PATH']). The external environment's path list (os.environ['PATH']) is used as a fallback if the key env['ENV']['PATH'] does not exist. On Windows systems, searches for executable programs with any of the file extensions listed in the pathext keyword argument, or if None (the default) the pathname extensions listed in the &consenv; (env['ENV']['PATHEXT']). The external environment's pathname extensions list (os.environ['PATHEXT']) is used as a fallback if the key env['ENV']['PATHEXT'] does not exist. When called as a global function, uses the external environment's path os.environ['PATH'] and path extensions os.environ['PATHEXT'], respectively, if path and pathext are None. Will not select any path name or names in the optional reject list.