Providing Help for Command-Line Build Variables 10.2.3. Controlling Command-Line Build Variables 10.2.2. Command-Line variable= value Build Variables 10.2.1. Adding Custom Command-Line Options: the AddOption Function 10.2.
Strings for Getting or Setting Values of SCons Command-Line Options 10.1.5. Setting Values of Command-Line Options: the SetOption Function 10.1.4. Getting Values Set by Command-Line Options: the GetOption Function 10.1.3. Not Having to Specify Command-Line Options Each Time: the SCONSFLAGS Environment Variable 10.1.2. Controlling a Build From the Command Line 10.1. Printing Detailed Build Status: the GetBuildFailures Function 10. Providing Build Progress Output: the Progress Function 9.4. Controlling How SCons Prints Build Commands: the $*COMSTR Variables 9.3.
Providing Build Help: the Help Function 9.2. Finding Installed Library Information: the ParseConfig Function 9. Separating Compile Arguments into their Variables: the ParseFlags Function 8.4. Merging Options While Creating Environment: the parse_flags Parameter 8.3. Merging Options into the Environment: the MergeFlags Function 8.2. Automatically Putting Command-line Options into their Construction Variables 8.1. Using the PyPackageDir function to add to the toolpath 8. Using sys.path within the toolpath 7.4.5. Providing an external directory to toolpath 7.4.3. Using the toolpath for external Tools 7.4.1. Adding to PATH Values in the Execution Environment 7.4. Propagating PATH From the External Environment 7.3.2. Controlling the Execution Environment for Issued Commands 7.3.1. Overriding Construction Variable Settings 7.3. Prepending Unique Values: the PrependUnique Method 7.2.14. Appending to the Beginning of Values: the Prepend Method 7.2.13. Appending Unique Values: the AppendUnique Method 7.2.12. Appending to the End of Values: the Append Method 7.2.11. Setting Values Only If They're Not Already Defined: the SetDefault Method 7.2.10. Replacing Values: the Replace Method 7.2.9. Making Copies of Construction Environments: the Clone Method 7.2.8. Multiple Construction Environments 7.2.7. Controlling the Default Construction Environment: the DefaultEnvironment Function 7.2.6. Handling Problems With Value Expansion 7.2.5. Expanding Values From a Construction Environment: the subst Method 7.2.4. Fetching Values From a Construction Environment 7.2.3. Creating a Construction Environment: the Environment Function 7.2.2. Using Values From the External Environment 7.2. Order-Only Dependencies: the Requires Function 6.8. Ignoring Dependencies: the Ignore Function 6.7. Dependencies From External Files: the ParseDependsįunction 6.6. Explicit Dependencies: the Depends Function 6.5. Implicit Dependencies: The $CPPPATH Construction Variable 6.3.
Mixing Different Ways of Deciding If a File Has Changed 6.2. Writing Your Own Custom Decider Function 6.1.5. Deciding If a File Has Changed Using Both MD Signatures and Time Stamps 6.1.4. Using Time Stamps to Decide If a File Has Changed 6.1.3. Using MD5 Signatures to Decide if a File Has Changed 6.1.2. Deciding When an Input File Has Changed: the Decider Function 6.1.1. GetBuildPath: Getting the Path From a Node or String 6. Using a Node's File Name as a String 5.5. Explicitly Creating File and Directory Nodes 5.3. Builder Methods Return Lists of Target Nodes 5.2. Finding Libraries: the $LIBPATH Construction Variable 5. Building Shared (DLL) Libraries: the SharedLibrary Builder 4.2. Building Static Libraries Explicitly: the StaticLibrary Builder 4.1.3.
#MAKE THE CUT 4.1.0 REGISTER CODE#
Building Libraries From Source Code or Object Files 4.1.2. Sharing Source Files Between Multiple Programs 4. Making Lists of Files Easier to Read 3.6. Specifying the Name of the Target (Output) File 3.2. Less Simple Things to Do With Builds 3.1. SCons Functions Are Order-Independent 2.6. SConstruct Files Are Python Scripts 2.5.2. Building and Installing SCons Without Administrative Privileges 2. Installing SCons in Other Locations 1.3.3. Building and Installing Multiple Versions of SCons Side-by-Side 1.3.2. Building and Installing SCons on Any System 1.3.1. A Caveat About This Guide's Completeness 3.
0 kommentar(er)
