Module SConf

ConfigureDryRunError
Raised when a file or directory needs to be updated during a Configure
process, but the user requested a dry-run

ConfigureCacheError
Raised when a use explicitely requested the cache feature, but the test
is run the first time.

SConfBuildInfo
Special build info for targets of configure tests. Additional members
are result (did the builder succeed last time?) and string, which
contains messages of the original build phase.

Streamer
'Sniffer' for a file-like writable object. Similar to the unix tool tee.

SConfBuildTask
This is almost the same as SCons.Script.BuildTask. Handles SConfErrors
correctly and knows about the current cache_mode.

SConfBase
This is simply a class to represent a configure context. After
creating a SConf object, you can call any tests. After finished with your
tests, be sure to call the Finish() method, which returns the modified
environment.
Some words about caching: In most cases, it is not necessary to cache
Test results explicitely. Instead, we use the scons dependency checking
mechanism. For example, if one wants to compile a test program
(SConf.TryLink), the compiler is only called, if the program dependencies
have changed. However, if the program could not be compiled in a former
SConf run, we need to explicitely cache this error.

CheckContext
Provides a context for configure tests. Defines how a test writes to the
screen and log file.

CheckLib(context,
library=None,
symbol='main',
header=None,
language=None,
autoadd=1)
A test for a library. See also CheckLibWithHeader.
Note that library may also be None to test whether the given symbol
compiles without flags.

CheckLibWithHeader(context,
libs,
header,
language,
call=None,
autoadd=1)
Another (more sophisticated) test for a library.
Checks, if library and header is available for language (may be 'C'
or 'CXX'). Call maybe be a valid expression _with_ a trailing ';'.
As in CheckLib, we support library=None, to test if the call compiles
without extra link flags.