aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/file.hxx
AgeCommit message (Collapse)AuthorFilesLines
2022-06-28Add support for rule-specific import phase 2Boris Kolpackov1-11/+18
For example: import! [metadata, rule_hint=cxx.link] lib = libhello%lib{hello}
2022-06-17Add ability to ignore subprojects in create_bootstrap_outer()Boris Kolpackov1-2/+3
2022-05-06Minor terminology fix in diagnostics and commentsBoris Kolpackov1-1/+1
2022-02-16Add pre/post hooks to load_root()Boris Kolpackov1-1/+7
2022-02-14Add ability to override amalgamation and subprojects in bootstrap_src()Boris Kolpackov1-1/+8
2021-12-15Return stable imported target name from import_direct()Boris Kolpackov1-6/+16
2021-04-02Add support for propagating project environmentBoris Kolpackov1-0/+4
2021-02-08Enter scope src directories into scope mapBoris Kolpackov1-1/+1
2020-07-12Cache subprojects variable value in scope::root_extraBoris Kolpackov1-7/+0
2020-07-09Add support for ad hoc importationBoris Kolpackov1-4/+31
2020-07-03Cutoff amalgamation and subproject for simple projectsBoris Kolpackov1-3/+2
2020-07-02Optimize variable extraction in bootstrap_src()Boris Kolpackov1-11/+8
2020-05-28Allow calling certain search_existing() versions during load phaseBoris Kolpackov1-1/+2
This is necessary for $target.path() implementation.
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-6/+4
2020-05-27Amalgamation cutoff supportBoris Kolpackov1-7/+10
Now a project that disables amalgamation will not logically "see" an outer project even if it's physically inside its scope.
2020-04-30Verify path set by {src,out}-root.build files is absoluteBoris Kolpackov1-2/+3
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-14/+168
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-27Don't switch projects when switching scopes during bootstrapBoris Kolpackov1-6/+16
2020-03-17Rework config::{omitted,required,optional}() into unified config_lookup()Boris Kolpackov1-10/+11
2020-03-13Cleanup and make config/utility.?xx part of build system coreBoris Kolpackov1-0/+14
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2019-11-11Use path_name for `-` to stdin/stdout translationKaren Arutyunov1-1/+1
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-0/+26
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-29Add forward declaration header for build state typesBoris Kolpackov1-4/+1
2019-08-25Split import into search and load stepsBoris Kolpackov1-0/+11
This allows us to load things in a separate context.
2019-08-23Introduce notion of build contextBoris Kolpackov1-11/+6
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-21Implement dynamic loading of build system modulesBoris Kolpackov1-1/+1
2019-08-16Minor cleanupsBoris Kolpackov1-19/+16
2019-07-01Split build system into library and driverBoris Kolpackov1-0/+243
generated by cgit v1.1 at 2024-11-01 00:59:02 +0000