Next: Introspection, Previous: Caching Results, Up: Controlling where ASDF searches for systems [Contents][Index]
The specified functions are exported from your build system’s package. Thus for ASDF the corresponding functions are in package ASDF, and for XCVB the corresponding functions are in package XCVB.
will read the configuration and initialize all internal variables.
You may extend or override configuration
from the environment and configuration files
with the given PARAMETER, which can be
nil (no configuration override),
or a SEXP (in the SEXP DSL),
a string (as in the string DSL),
a pathname (of a file or directory with configuration),
or a symbol (fbound to function that when called returns one of the above).
undoes any source registry configuration
and clears any cache for the search algorithm.
You might want to call this function
(or better, clear-configuration)
before you dump an image that would be resumed
with a different configuration,
and return an empty configuration.
Note that this does not include clearing information about
systems defined in the current image, only about
where to look for systems not yet defined.
checks whether a source registry has been initialized. If not, initialize it with the given PARAMETER.
Every time you use ASDF’s find-system, or
anything that uses it (such as operate, load-system, etc.),
ensure-source-registry is called with parameter nil,
which the first time around causes your configuration to be read.
If you change a configuration file,
you need to explicitly initialize-source-registry again,
or maybe simply to clear-source-registry (or clear-configuration)
which will cause the initialization to happen next time around.
Next: Introspection, Previous: Caching Results, Up: Controlling where ASDF searches for systems [Contents][Index]