aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/config
AgeCommit message (Collapse)AuthorFilesLines
2019-11-15Generalize attributes to be comma-separated with arbitrary valuesBoris Kolpackov1-3/+3
Before: x = [string null] After: x = [string, null]
2019-11-14Make use of butl::to_stream(ostream, path, bool)Karen Arutyunov1-1/+4
2019-11-13Implement config.config.persist logicBoris Kolpackov4-78/+193
Note that the inherited value part is documented but is not yet fully implemented.
2019-11-12Infra work for customizable config var persistence (config.config.persist)Boris Kolpackov4-40/+74
2019-11-12Rename config.{import,export} to config.config.{load,save}Boris Kolpackov4-47/+51
Also rename the $config.export() function to $config.save().
2019-11-12Rename config.module to config.config.moduleBoris Kolpackov2-12/+12
The old name was an accidental land-grab.
2019-11-11Change default for unused config.import.* variables from drop to keepBoris Kolpackov4-34/+94
2019-11-11Use path_name for `-` to stdin/stdout translationKaren Arutyunov1-7/+5
2019-11-07Add libbuild2/config/.gitignore with host-config.cxxBoris Kolpackov1-0/+1
2019-11-07Initial work on path_name use for `-` to stdin/stdout translationBoris Kolpackov5-22/+29
2019-11-04Add support for ~host special configuration name in config.importBoris Kolpackov2-5/+50
This is the "default host configuration" that corresponds to how the build system itself was built. For example: $ b create: tools/,cc config.import=~host
2019-11-04Add $config.export() functionBoris Kolpackov7-73/+165
This is similar to the config.export variable functionality except it can be called from within buildfiles. Note that this function can only be used during configure unless the config module creation was forced for other meta-operations with config.module=true in bootstrap.build.
2019-11-04Add support for configuration exporting and importingBoris Kolpackov3-130/+244
The new config.export variable specifies the alternative file to write the configuration to as part of the configure meta-operation. For example: $ b configure: proj/ config.export=proj-config.build The config.export value "applies" only to the projects on whose root scope it is specified or if it is a global override (the latter is a bit iffy but we allow it, for example, to dump everything to stdout). This means that in order to save a subproject's configuration we will have to use a scope-specific override (since the default will apply to the outermost amalgamation). For example: $ b configure: subproj/ subproj/config.export=.../subproj-config.build This could be somewhat unnatural but then it will be the amalgamation whose configuration we normally want to export. The new config.import variable specifies additional configuration files to be loaded after the project's default config.build, if any. For example: $ b create: cfg/,cc config.import=my-config.build Similar to config.export, the config.import value "applies" only to the project on whose root scope it is specified or if it is a global override. This allows the use of the standard override "positioning" machinery (i.e., where the override applies) to decide where the extra configuration files are loaded. The resulting semantics is quite natural and consistent with command line variable overrides, for example: $ b config.import=.../config.build # outermost amalgamation $ b ./config.import=.../config.build # this project $ b !config.import=.../config.build # every project Both config.export and config.import recognize the special `-` file name as an instruction to write/read to/from stdout/stdin, respectively. For example: $ b configure: src-prj/ config.export=- | b configure: dst-prj/ config.import=-
2019-10-29Add forward declaration header for build state typesBoris Kolpackov1-2/+1
2019-10-23Expand commentBoris Kolpackov1-2/+2
2019-10-18Optimize config::required() to move default value if possibleBoris Kolpackov2-6/+9
2019-08-28Add/update some module descriptionsKaren Arutyunov1-0/+5
2019-08-23Introduce notion of build contextBoris Kolpackov6-114/+126
All non-const global state is now in class context and we can now have multiple independent builds going on at the same time.
2019-08-21Cleanup context.hxx and its usageBoris Kolpackov1-1/+1
2019-07-24Use CLI-generated classes to parse testscript builtin optionsKaren Arutyunov2-2/+2
2019-07-24Move in build system module to separate libraryBoris Kolpackov2-5/+11
2019-07-05Move config, dist, test, and install modules into libraryKaren Arutyunov9-0/+1920