aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/config/utility.hxx
AgeCommit message (Collapse)AuthorFilesLines
2021-04-07Register environment variables for hermetic build configurationsBoris Kolpackov1-2/+81
2021-03-26Implement config.config.environment storageBoris Kolpackov1-0/+2
2020-09-24Add ability to ignore extra variables in specified_config()Boris Kolpackov1-2/+12
2020-08-18Add ability to mark config.* variables as "unsaved" (always transient)Boris Kolpackov1-1/+13
2020-08-16Add support for post-configure and pre-disfigure hooksBoris Kolpackov1-7/+40
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-08Document project-specific configuration supportBoris Kolpackov1-1/+1
2020-03-31Handle duplicate config directives for same variableBoris Kolpackov1-1/+2
2020-03-27Implement project configuration reporting, similar to build system modulesBoris Kolpackov1-2/+2
2020-03-19Tweak lookup_config() semantics some moreBoris Kolpackov1-3/+11
2020-03-17Rework config::{omitted,required,optional}() into unified config_lookup()Boris Kolpackov1-79/+148
2020-03-13Cleanup and make config/utility.?xx part of build system coreBoris Kolpackov1-40/+66
2020-03-11Minor config variable lookup cleanupsBoris Kolpackov1-28/+30
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-01-27Fix typoBoris Kolpackov1-1/+1
2019-11-12Infra work for customizable config var persistence (config.config.persist)Boris Kolpackov1-0/+1
2019-10-29Add forward declaration header for build state typesBoris Kolpackov1-2/+1
2019-10-18Optimize config::required() to move default value if possibleBoris Kolpackov1-4/+7
2019-08-23Introduce notion of build contextBoris Kolpackov1-3/+3
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-07-24Use CLI-generated classes to parse testscript builtin optionsKaren Arutyunov1-1/+1
2019-07-05Move config, dist, test, and install modules into libraryKaren Arutyunov1-0/+179