aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/context.cxx
AgeCommit message (Collapse)AuthorFilesLines
2021-05-12Deal with helper thread starvation during phase switchingBoris Kolpackov1-19/+41
The implemented solution entails shadowing old phase queues so that helpers don't pick up old phase tasks and boosting the max_threads count so that we can create more helpers if all the existing ones are stuck in the old phase.
2021-05-12Keep phase locked while working own queueBoris Kolpackov1-11/+19
2021-05-05Deactivate when blocked on load phase mutexBoris Kolpackov1-2/+12
This turned out to be important when building in multiple contexts that share the scheduler (e.g., main and module/recipe build context). In this case we need an accurate active thread count in order to decide when to start an extra helper thread past max_active.
2021-03-19Redo entering of src directories into scope_mapBoris Kolpackov1-3/+3
2021-03-16Define intermediate build results file cache interfaceBoris Kolpackov1-0/+2
2021-02-08Enter scope src directories into scope mapBoris Kolpackov1-2/+2
2021-01-15Disable questionable unused functionalityBoris Kolpackov1-0/+2
2020-09-22Add ability to skip external modules during bootstrap (--no-external-modules)Boris Kolpackov1-0/+2
2020-06-29Add legal{} target type and config.install.legal variableBoris Kolpackov1-0/+1
This allows separation of legal files (LICENSE, AUTHORS, etc) from other documentation. For example: ./: ... doc{README} legal{LICENSE} $ b install ... config.install.legal=/usr/share/licenses/hello/
2020-06-01Extend target metadata to include variable prefix, stable nameBoris Kolpackov1-2/+2
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-1/+11
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-1/+4
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-03-31Tweak variable patterns not to break overridesBoris Kolpackov1-29/+32
2020-03-31Switch to project variable visibility by defaultBoris Kolpackov1-81/+99
2020-03-18Pattern-type config.** variables with global visibility by defaultBoris Kolpackov1-43/+42
2020-03-13Cleanup and make config/utility.?xx part of build system coreBoris Kolpackov1-8/+2
2020-02-11Add match_only flag to contextBoris Kolpackov1-0/+2
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-07Initial work on path_name use for `-` to stdin/stdout translationBoris Kolpackov1-1/+2
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-1/+1
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-22Implement loaded_modules state lockingBoris Kolpackov1-1/+3
This would be necessary if someone runs two parallel top-level contexts.
2019-10-22Rename global_mutex_shards to global_mutexesBoris Kolpackov1-2/+2
2019-10-22Move global mutex shards to contextBoris Kolpackov1-0/+2
2019-08-28Redo build_installed without requiring linking whole archiveBoris Kolpackov1-1/+3
2019-08-27Propagate global var overrides to module build contextBoris Kolpackov1-0/+7
2019-08-27Redo module context pointerBoris Kolpackov1-3/+5
2019-08-27Don't set import.build2 variable in cross-compiled build2Karen Arutyunov1-1/+1
2019-08-26Implement auto-import of development build2 buildBoris Kolpackov1-0/+10
2019-08-26Implement updating build system modulesBoris Kolpackov1-3/+9
2019-08-26Make target types project-wideBoris Kolpackov1-5/+8
2019-08-23Introduce notion of build contextBoris Kolpackov1-414/+396
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-183/+32
2019-08-21Implement dynamic loading of build system modulesBoris Kolpackov1-4/+1
2019-08-20Add build.version.interfaceBoris Kolpackov1-0/+11
This build system interface version should be embedded into build system modules as load_suffix.
2019-08-19Minor cleanupsBoris Kolpackov1-48/+50
2019-08-07Distinguish between internal/external wait deactivation in schedulerBoris Kolpackov1-4/+4
This turns out to be necessary for the deadlock detection to work properly.
2019-07-01Split build system into library and driverBoris Kolpackov1-0/+1026
generated by cgit v1.1 at 2024-04-28 10:47:00 +0000