aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/context.hxx
AgeCommit message (Collapse)AuthorFilesLines
2024-08-21Don't work own queue in wait_guard dtorBoris Kolpackov1-1/+1
There is suspicion this causes a deadlock for reasons so far unclear. See also GH issue #319.
2024-02-26Add ability to request serialization from schedulerBoris Kolpackov1-2/+8
In particular, this can be used to make sure no other recipe is being executed in parallel with the caller.
2023-11-01Add support for adjusting match options of post hoc prerequisitesBoris Kolpackov1-1/+7
2023-06-01Resolve (but disable for now) target_count issue in resolve_members()Boris Kolpackov1-1/+2
2023-05-29Disable counts verification if matched but not executed in resolve_members()Boris Kolpackov1-1/+3
2023-05-09Add --load-only option in addition to --match-onlyBoris Kolpackov1-3/+13
This option has the effect of loading all the subdirectory buildfiles that are not explicitly included.
2023-04-19Fix several issues in build system module importation logicmodule-importBoris Kolpackov1-6/+6
2023-04-13Various minor generalizations for in-process configure support in bpkgBoris Kolpackov1-2/+26
2023-04-05Allow creating context with bare minimum of initializationsBoris Kolpackov1-4/+13
This is used by bpkg to detect forwarded configurations without incurring the full context creation overhead.
2023-03-01Add support for installation manifestBoris Kolpackov1-0/+16
2022-12-15Add noexcept to move constructors and move assignment operatorsKaren Arutyunov1-2/+2
2022-11-30Reserve targets, variables to avoid rehashingBoris Kolpackov1-0/+17
2022-11-29Fix backlink logic for target groupsBoris Kolpackov1-3/+14
We used to backlink ad hoc group members both via the group and as individual members. And for explicit groups it was done only via individual members, which means it only works correctly if every member is individually updated. Now both types of groups are backlinked from the group target.
2022-10-28Add ability to disable diagnostics buffering (--no-diag-buffer)Boris Kolpackov1-0/+5
2022-10-19Add support for post hoc prerequisitesBoris Kolpackov1-5/+22
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-13Fix couple of corner cases in public/private variable modelBoris Kolpackov1-43/+47
2022-10-13Switch to public/private variables modelBoris Kolpackov1-7/+6
Now unqualified variables are project-private and can be typified.
2022-10-11Factor variable patterns out of variable_pool into separate variable_patternsBoris Kolpackov1-1/+2
We have patterns only for the public variables pool.
2022-10-10Preparatory work for public/private variable distinctionBoris Kolpackov1-1/+1
We still always use the public var_pool from context but where required, all access now goes through scope::var_pool().
2022-09-12Add note on backlink=overwrite modeBoris Kolpackov1-1/+23
2022-06-29Rework pkg-config variable naming, use build2.metadata as general indicatorBoris Kolpackov1-4/+6
2022-06-21Add --trace-{match,execute} optionsBoris Kolpackov1-0/+11
These options can be used to understand which dependency chain causes matching or execution of a particular target.
2022-05-23Cache build.host value in contextBoris Kolpackov1-0/+4
2022-04-20Add import cacheBoris Kolpackov1-0/+20
2022-04-15Omit unnecessary clearing of cached base_scope valuesBoris Kolpackov1-1/+6
2022-04-13Cache target base scope lookupsBoris Kolpackov1-2/+8
2022-04-08Fix race in phase lock contention countingBoris Kolpackov1-1/+2
2022-04-08Add phase switch contention to build statisticsBoris Kolpackov1-1/+6
2022-03-08Add update=execute special value for cases where it's not defaultBoris Kolpackov1-2/+4
2022-03-07Fix operation-specific variables logic for inner/outer operationsBoris Kolpackov1-1/+5
2022-03-02Add update operation-specific variable with unmatch|match additional valuesBoris Kolpackov1-8/+28
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.
2022-02-14Factor reusable code to contex::enter_project_overrides()Boris Kolpackov1-0/+7
2022-02-10Make few global types separately constructible/initializableBoris Kolpackov1-2/+12
2021-10-07Allow forcing installation of exe{} prerequisites of file targetsBoris Kolpackov1-1/+1
This can be achieved with prerequisite-specific install=true, for example: exe{foo}: exe{bar}: install = true # foo runs bar
2021-09-20Add support for disabling clean through target-prerequisite relationshipBoris Kolpackov1-0/+12
Our current semantics is to clean any prerequisites that are in the same project (root scope) as the target and it may seem more natural to rather only clean prerequisites that are in the same base scope. While it's often true for simple projects, in more complex cases it's not unusual to have common intermediate build results (object files, utility libraries, etc) reside in the parent and/or sibling directories. With such arrangements, cleaning only in base (even from the project root) may leave such intermediate build results laying around (since there is no reason to list them as prerequisites of any directory aliases). So we clean in the root scope by default but now any target-prerequisite relationship can be marked not to trigger a clean with the clean=false prerequisite-specific value.
2021-05-12Deal with helper thread starvation during phase switchingBoris Kolpackov1-5/+7
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-2/+6
2021-05-07Various improvements and clarifications in metadata handlingBoris Kolpackov1-3/+4
2021-03-16Define intermediate build results file cache interfaceBoris Kolpackov1-0/+3
2021-01-15Disable questionable unused functionalityBoris Kolpackov1-1/+3
2020-11-11Add context::current_action()Boris Kolpackov1-1/+9
2020-09-22Add ability to skip external modules during bootstrap (--no-external-modules)Boris Kolpackov1-0/+5
2020-08-16Add support for post-configure and pre-disfigure hooksBoris Kolpackov1-0/+10
2020-06-09Make metadata variable prefix mandatoryBoris Kolpackov1-4/+2
While we could automatically set it if the target is imported, there is nothing we can do if the target is used in the same project. So to avoid confusion we make it mandatory.
2020-06-02Add process_path_ex with program stable name and checksumBoris Kolpackov1-0/+2
2020-06-01Extend target metadata to include variable prefix, stable nameBoris Kolpackov1-3/+25
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-5/+14
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-0/+5
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-13Cleanup and make config/utility.?xx part of build system coreBoris Kolpackov1-12/+0
2020-02-11Add match_only flag to contextBoris Kolpackov1-0/+5
generated by cgit v1.1 at 2024-11-14 16:04:29 +0000