Config file

Added by David Cowan over 1 year ago

Is the config file format/capability documented anywhere?
I see in another thread that functionality has been added to override the c-compilers folder -- what else can be done in there?


Replies (2)

RE: Config file - Added by Joshua Jensen over 1 year ago

It is not documented yet, and that is the primary reason why JamPlus is not 1.0.

The following Config options are currently available. I'll give an ever so brief description below.

  • Compiler - Compiler override. Same as passing in -compiler on the jam --workspace command line
  • Configurations - A list of valid configurations
  • JambaseText - Text added verbatim to the generated Jambase.jam with the addition of prepended sourceRootPath and destinationRootPath variables.
  • JambaseVariables - A table of key/value table pairs { 'key', 'value'} that are added to the out of source build directory's Jambase.jam. Supports $(var) expansion in the value part.
  • JamfileVariables - A table of key/value table pairs { 'key', 'value'} that are added to the out of source build directory's Jamfile.jam. Supports $(var) expansion in the value part.
  • JamModulesUserPath - A string or table of strings describing the extra locations to look for Jam modules (including the c-compilers/ folder).
  • Platforms - A list of valid platforms
  • SubIncludes - A table of { "ROOT_NAME", "path", "JamfileName", true to SubInclude ROOT_NAME : JamfileName }. Defaults to { 'AppRoot', '"$(sourceRootPath)"', sourceJamfile }.

I have other ones I would like to add, but those tend to come as need arises.

RE: Config file - Added by David Cowan over 1 year ago

Awesome... thanks.

The JamModulesUserPath one has already come in very handy :)

(1-2/2)