aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/config
AgeCommit message (Collapse)AuthorFilesLines
2021-02-08Enter scope src directories into scope mapBoris Kolpackov1-1/+1
2021-01-30Add std::{map, multimap} to types.hxxBoris Kolpackov2-5/+1
Seeing that std::map is becoming a common Buildfile variable type.
2020-12-04Mark Buildfile functions as pure or impureBoris Kolpackov1-1/+3
2020-12-02Fix bug in config utilityBoris Kolpackov1-2/+3
2020-09-24Give hints for common causes of "no rule to update ..." errorBoris Kolpackov1-1/+1
2020-09-24Add ability to ignore extra variables in specified_config()Boris Kolpackov2-9/+33
2020-08-18Add ability to mark config.* variables as "unsaved" (always transient)Boris Kolpackov5-19/+40
2020-08-16Add support for post-configure and pre-disfigure hooksBoris Kolpackov6-27/+121
2020-08-16Add ability to initialize bootstrapped modules after loading root.buildBoris Kolpackov1-2/+4
2020-07-12Cache subprojects variable value in scope::root_extraBoris Kolpackov1-8/+8
2020-07-02Optimize variable extraction in bootstrap_src()Boris Kolpackov1-4/+3
2020-06-12Make order of imports stable in saved host build configurationBoris Kolpackov1-4/+4
2020-06-05Add ability to specify ad hoc recipe actionsBoris Kolpackov1-1/+1
We are reusing the buildspec syntax for that.
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-2/+2
2020-05-27Amalgamation cutoff supportBoris Kolpackov1-4/+2
Now a project that disables amalgamation will not logically "see" an outer project even if it's physically inside its scope.
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-0/+14
Specifically, now config.<tool> (like config.cli) is handled by the import machinery (it is like a shorter alias for config.import.<tool>.<tool>.exe that we already had). And the cli module now uses that instead of custom logic. This also adds support for uniform tool metadata extraction that is handled by the import machinery. As a result, a tool that follows the "build2 way" can be imported with metadata by the buildfile and/or corresponding module without any tool-specific code or brittleness associated with parsing --version or similar outputs. See the cli tool/module for details. Finally, two new flavors of the import directive are now supported: import! triggers immediate importation skipping any rule-specific logic while import? is optional import (analogous to using?). Note that optional import is always immediate. There is also the import-specific metadata attribute which can be specified for these two import flavors in order to trigger metadata importation. For example: import? [metadata] cli = cli%exe{cli} if ($cli != [null]) info "cli version $($cli:cli.version)"
2020-04-27Add utility config::{assign,append}_config() functionsBoris Kolpackov1-1/+43
2020-04-27Don't switch projects when switching scopes during bootstrapBoris Kolpackov1-1/+4
2020-04-08Document project-specific configuration supportBoris Kolpackov1-1/+1
2020-04-02Fix ~host config to only contain cc and bin modules configurationBoris Kolpackov2-3/+7
Also add ~build2 that contains everything (except config.dist.*) to be used for build system modules.
2020-03-31Handle duplicate config directives for same variableBoris Kolpackov1-1/+2
2020-03-31Switch to project variable visibility by defaultBoris Kolpackov1-2/+4
2020-03-27Implement project configuration reporting, similar to build system modulesBoris Kolpackov1-2/+2
2020-03-19Tweak lookup_config() semantics some moreBoris Kolpackov2-6/+36
2020-03-18Pattern-type config.** variables with global visibility by defaultBoris Kolpackov2-13/+20
2020-03-17Rename all find*(variable) to lookup*(variable)Boris Kolpackov3-9/+9
Now we consistently use term "lookup" for variable value lookup. At some point we should also rename type lookup to binding and get rid of all the lookup_type aliases.
2020-03-17Rework config::{omitted,required,optional}() into unified config_lookup()Boris Kolpackov5-104/+251
2020-03-13Cleanup and make config/utility.?xx part of build system coreBoris Kolpackov7-227/+111
2020-03-11Minor config variable lookup cleanupsBoris Kolpackov5-45/+46
2020-03-04Fix bug in config.config.persist logicBoris Kolpackov2-2/+10
2020-02-07Drop copyright notice from source codeKaren Arutyunov11-11/+0
2020-01-29Rename module_base to module, redo module boot/init argument passingBoris Kolpackov3-26/+11
2020-01-28Use scope::var_pool()Boris Kolpackov2-5/+5
2020-01-28Use scope::insert_rule()Boris Kolpackov1-14/+8
2020-01-27Improve module loading APIBoris Kolpackov2-4/+4
2020-01-27Fix typoBoris Kolpackov1-1/+1
2019-11-15Use path_name_view in location and path_name_value in location_valueKaren Arutyunov1-1/+1
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=-