aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/config/operation.cxx
AgeCommit message (Collapse)AuthorFilesLines
2024-10-08Expose custom save function in config moduleBoris Kolpackov1-1/+1
It can generally be useful, for example, to complete relative paths before saving them to config.build (if abs_dir_path does not fit).
2024-07-31Add cross-reference noteBoris Kolpackov1-0/+3
2024-04-11Diagnose empty paths in config.config.{load,save}Boris Kolpackov1-2/+6
GitHub issue #372.
2024-02-06Fix bunch of maybe used uninitialized warningsBoris Kolpackov1-1/+2
2023-05-31Improve diagnostics when dropping config.import.* valuesBoris Kolpackov1-0/+20
2023-04-19Clarify const-ness issues in configure implementationBoris Kolpackov1-10/+20
2023-04-13Various minor generalizations for in-process configure support in bpkgBoris Kolpackov1-0/+6
2023-03-01Add support for installation manifestBoris Kolpackov1-0/+6
2022-12-14Improve empty simple value to empty list of names reduction heuristicsBoris Kolpackov1-2/+2
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-11-16Initial low verbosity diagnostics reworkBoris Kolpackov1-6/+11
2022-10-19Add support for post hoc prerequisitesBoris Kolpackov1-2/+4
Unlike normal and ad hoc prerequisites, a post hoc prerequisite is built after the target, not before. It may also form a dependency cycle together with normal/ad hoc prerequisites. In other words, all this form of dependency guarantees is that a post hoc prerequisite will be built if its dependent target is built. See the NEWS file for details and an example.
2022-10-10Preparatory work for public/private variable distinctionBoris Kolpackov1-0/+8
We still always use the public var_pool from context but where required, all access now goes through scope::var_pool().
2022-06-14Tighten value::extra usage in config moduleBoris Kolpackov1-2/+2
Specifically, only values marked with 1 are treated as default leaving other values for use for other purposes.
2022-04-19Switch to using std::function for target::data_padBoris Kolpackov1-2/+2
2022-04-07Rename {match,execute}() to *_sync(), add *_complete()Boris Kolpackov1-1/+1
In particular, the match() rename makes sure it doesn't clash with rule::match() which, after removal of the hint argument in simple_rule, has exactly the same signature, thus making it error-prone to calling recursively.
2022-03-29Add variable_map::lookup_namespace(string) overloadBoris Kolpackov1-1/+1
2022-02-16Invent quoting modes for to_stream(name)Karen Arutyunov1-3/+3
2021-12-16Pass context to (meta-)operation hooksBoris Kolpackov1-4/+4
2021-09-20Assign pre-defined semantics to config.<project>.develop variablesBoris Kolpackov1-5/+24
This variable allows a project to distinguish between development and consumption builds. While normally there is no distinction between these two modes, sometimes a project may need to provide additional functionality during development. For example, a source code generator which uses its own generated code in its implementation may need to provide a bootstrap step from the pre-generated code. Normally, such a step is only needed during development. See "Project Configuration" in the manual for details.
2021-04-09Fix bug in configure meta-operation implementationBoris Kolpackov1-1/+1
2021-04-04Add base functionality for hermetic build configurationshermeticBoris Kolpackov1-30/+110
2021-03-26Implement config.config.environment storageBoris Kolpackov1-96/+147
2021-03-19Redo entering of src directories into scope_mapBoris Kolpackov1-4/+4
2021-02-08Enter scope src directories into scope mapBoris Kolpackov1-1/+1
2021-01-30Add std::{map, multimap} to types.hxxBoris Kolpackov1-2/+0
Seeing that std::map is becoming a common Buildfile variable type.
2020-09-24Give hints for common causes of "no rule to update ..." errorBoris Kolpackov1-1/+1
2020-08-18Add ability to mark config.* variables as "unsaved" (always transient)Boris Kolpackov1-4/+8
2020-08-16Add support for post-configure and pre-disfigure hooksBoris Kolpackov1-0/+16
2020-07-12Cache subprojects variable value in scope::root_extraBoris Kolpackov1-8/+8
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-03-17Rename all find*(variable) to lookup*(variable)Boris Kolpackov1-4/+4
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 Kolpackov1-5/+5
2020-03-13Cleanup and make config/utility.?xx part of build system coreBoris Kolpackov1-2/+2
2020-03-11Minor config variable lookup cleanupsBoris Kolpackov1-3/+3
2020-03-04Fix bug in config.config.persist logicBoris Kolpackov1-1/+9
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-01-27Improve module loading APIBoris Kolpackov1-2/+2
2019-11-15Generalize attributes to be comma-separated with arbitrary valuesBoris Kolpackov1-3/+3
Before: x = [string null] After: x = [string, null]
2019-11-13Implement config.config.persist logicBoris Kolpackov1-76/+153
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-33/+41
2019-11-12Rename config.{import,export} to config.config.{load,save}Boris Kolpackov1-25/+24
Also rename the $config.export() function to $config.save().
2019-11-11Change default for unused config.import.* variables from drop to keepBoris Kolpackov1-16/+70
2019-11-07Initial work on path_name use for `-` to stdin/stdout translationBoris Kolpackov1-16/+17
2019-11-04Add $config.export() functionBoris Kolpackov1-30/+48
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-99/+165
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-23Expand commentBoris Kolpackov1-2/+2
2019-08-23Introduce notion of build contextBoris Kolpackov1-95/+107
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-05Move config, dist, test, and install modules into libraryKaren Arutyunov1-0/+997
generated by cgit v1.1 at 2024-12-19 22:48:46 +0000