aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/config/init.cxx
AgeCommit message (Collapse)AuthorFilesLines
2024-04-01Add ~host-no-warnings and ~build2-no-warnings special configurationsBoris Kolpackov1-2/+12
These are parallel to ~host and ~build2 but with suppressed C/C++ compiler warnings. Note also that the C++ ad hoc recipes are now by default built in ~build2-no-warnings instead of ~build2 unless the project is configured for development with config.<project>.develop=true.
2023-09-20Fix issue with fallback rule priority in dist moduleBoris Kolpackov1-9/+13
While at it, also remove workarounds for the same issue in the config and test modules.
2022-12-14Improve empty simple value to empty list of names reduction heuristicsBoris Kolpackov1-1/+1
Specifically, do not reduce typed RHS empty simple values for prepend/append and additionally for assignment provided LHS is typed and is a container.
2022-12-09Handle file opening error in config.config.loadBoris Kolpackov1-2/+9
2022-10-13Optimize by going straight to public variable pool where applicableBoris Kolpackov1-2/+5
2022-09-16Register fallback dist meta-operation rule for out of project targetsBoris Kolpackov1-2/+4
The problematic scenario this fixes is an ad hoc pattern rule (which we register for dist in order to inject any additional sources; see parser.cxx for details) that pulls a tool imported from the system (say /usr/bin/xxd).
2022-05-22Add support for variable patterns in config.config.disfigureBoris Kolpackov1-5/+116
2022-05-19Add config.config.unload variable to omit loading config.buildBoris Kolpackov1-7/+34
Note that the configuration is still loaded from config.config.load if specified. Note also that similar to config.config.load, only values specified on this project's root scope and global scope are considered.
2022-04-06Add support for rule hintsBoris Kolpackov1-3/+2
A rule hint is a target attribute, for example: [rule_hint=cxx] exe{hello}: c{hello} Rule hints can be used to resolve ambiguity when multiple rules match the same target as well as to override an unambiguous match.
2022-03-29Add variable_map::lookup_namespace(string) overloadBoris Kolpackov1-4/+0
2022-03-23Add note on disfig.* variables ideaBoris Kolpackov1-0/+16
2022-03-22Add ability to disfigure specific configuration variablesBoris Kolpackov1-0/+27
The new config.config.disfigure variable can be used to specify the list of variables to ignore when loading config.build (and any files specified in config.config.load), letting them to take on the default values. For example: $ b configure config.config.disfigure=config.hello.fancy
2021-04-22Incorporate project environment checksum into cc::compiler_info cache keyBoris Kolpackov1-1/+7
2021-04-07Register environment variables for hermetic build configurationsBoris Kolpackov1-0/+1
2021-04-04Add base functionality for hermetic build configurationshermeticBoris Kolpackov1-73/+133
2021-04-02Add support for propagating project environmentBoris Kolpackov1-2/+84
2021-03-26Implement config.config.environment storageBoris Kolpackov1-0/+87
2020-08-16Add support for post-configure and pre-disfigure hooksBoris Kolpackov1-20/+25
2020-08-16Add ability to initialize bootstrapped modules after loading root.buildBoris Kolpackov1-2/+4
2020-07-02Optimize variable extraction in bootstrap_src()Boris Kolpackov1-4/+3
2020-04-27Don't switch projects when switching scopes during bootstrapBoris Kolpackov1-1/+4
2020-04-02Fix ~host config to only contain cc and bin modules configurationBoris Kolpackov1-3/+6
Also add ~build2 that contains everything (except config.dist.*) to be used for build system modules.
2020-03-31Switch to project variable visibility by defaultBoris Kolpackov1-2/+4
2020-03-18Pattern-type config.** variables with global visibility by defaultBoris Kolpackov1-11/+18
2020-03-13Cleanup and make config/utility.?xx part of build system coreBoris Kolpackov1-1/+2
2020-03-11Minor config variable lookup cleanupsBoris Kolpackov1-1/+1
2020-03-04Fix bug in config.config.persist logicBoris Kolpackov1-1/+1
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-01-29Rename module_base to module, redo module boot/init argument passingBoris Kolpackov1-13/+10
2020-01-28Use scope::var_pool()Boris Kolpackov1-2/+2
2020-01-28Use scope::insert_rule()Boris Kolpackov1-14/+8
2019-11-15Use path_name_view in location and path_name_value in location_valueKaren Arutyunov1-1/+1
2019-11-13Implement config.config.persist logicBoris Kolpackov1-1/+29
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 Kolpackov1-7/+28
2019-11-12Rename config.{import,export} to config.config.{load,save}Boris Kolpackov1-15/+20
Also rename the $config.export() function to $config.save().
2019-11-12Rename config.module to config.config.moduleBoris Kolpackov1-10/+10
The old name was an accidental land-grab.
2019-11-11Change default for unused config.import.* variables from drop to keepBoris Kolpackov1-7/+7
2019-11-11Use path_name for `-` to stdin/stdout translationKaren Arutyunov1-7/+5
2019-11-07Initial work on path_name use for `-` to stdin/stdout translationBoris Kolpackov1-1/+4
2019-11-04Add support for ~host special configuration name in config.importBoris Kolpackov1-5/+37
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 Kolpackov1-6/+25
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 Kolpackov1-30/+78
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-08-23Introduce notion of build contextBoris Kolpackov1-5/+5
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-24Move in build system module to separate libraryBoris Kolpackov1-4/+10
2019-07-05Move config, dist, test, and install modules into libraryKaren Arutyunov1-0/+159
generated by cgit v1.1 at 2024-12-16 09:07:02 +0000