aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/operation.cxx
AgeCommit message (Collapse)AuthorFilesLines
2022-11-08Tweak match progress reporting for serial executionBoris Kolpackov1-1/+3
2022-10-20Implement parallel execution of post hoc prerequisitesBoris Kolpackov1-7/+46
2022-10-19Add support for post hoc prerequisitesBoris Kolpackov1-35/+164
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-13Switch to public/private variables modelBoris Kolpackov1-3/+0
Now unqualified variables are project-private and can be typified.
2022-09-27Improve diagnostics for multiple targets sharing pathBoris Kolpackov1-3/+13
2022-04-15Tweak match progress display parametersBoris Kolpackov1-1/+1
2022-04-15Throttle progress display during matchBoris Kolpackov1-8/+31
2022-04-07Rename {match,execute}() to *_sync(), add *_complete()Boris Kolpackov1-1/+4
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-11Add JSON format support for --structured-result option and info meta operationKaren Arutyunov1-6/+211
2022-03-02Add update operation-specific variable with unmatch|match additional valuesBoris Kolpackov1-0/+3
Note that the unmatch (match but do not update) and match (update during match) values are only supported by certain rules (and potentially only for certain prerequisite types). Additionally: - All operation-specific variables are now checked for false as an override for the prerequisite-specific include value. In particular, this can now be used to disable a prerequisite for update, for example: ./: exe{test}: update = false - The cc::link_rule now supports the update=match value for headers and ad hoc prerequisites. In particular, this can be used to make sure all the library headers are updated before matching any of its (or dependent's) object files.
2021-12-16Verify targets that alias same path are read-onlyBoris Kolpackov1-1/+113
2021-12-16Pass context to (meta-)operation hooksBoris Kolpackov1-1/+1
2021-10-16Improve info meta-operation not to print trailing spacesBoris Kolpackov1-8/+22
2021-09-16Fix over-tight assumption in standard operation match()Boris Kolpackov1-0/+1
2021-08-02Print list of bootstrapped modules in info meta-operationBoris Kolpackov1-1/+10
2021-03-19Redo entering of src directories into scope_mapBoris Kolpackov1-2/+4
2020-10-20Add operation callback for adhoc rule match and applyBoris Kolpackov1-0/+6
2020-08-25Fix bug in interaction of unmatch logic with target groupsBoris Kolpackov1-0/+15
2020-07-12Cache subprojects variable value in scope::root_extraBoris Kolpackov1-1/+1
2020-07-09Add support for ad hoc importationBoris Kolpackov1-1/+1
2020-07-02Cache project name in root_extraBoris Kolpackov1-1/+1
2020-05-27Suppress skip count diagnostics if no progress was requestedBoris Kolpackov1-2/+5
2020-05-27Amalgamation cutoff supportBoris Kolpackov1-1/+1
Now a project that disables amalgamation will not logically "see" an outer project even if it's physically inside its scope.
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-7/+7
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-23Un-tune scheduler when building build system modulesBoris Kolpackov1-77/+82
2019-08-23Introduce notion of build contextBoris Kolpackov1-47/+56
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-0/+1
2019-07-01Split build system into library and driverBoris Kolpackov1-0/+617
generated by cgit v1.1 at 2024-11-01 12:09:07 +0000