| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2023-04-13 | Various minor generalizations for in-process configure support in bpkg | Boris Kolpackov | 1 | -2/+26 | |
| 2023-04-05 | Allow creating context with bare minimum of initializations | Boris Kolpackov | 1 | -4/+13 | |
| This is used by bpkg to detect forwarded configurations without incurring the full context creation overhead. | |||||
| 2023-03-01 | Add support for installation manifest | Boris Kolpackov | 1 | -0/+16 | |
| 2022-12-15 | Add noexcept to move constructors and move assignment operators | Karen Arutyunov | 1 | -2/+2 | |
| 2022-11-30 | Reserve targets, variables to avoid rehashing | Boris Kolpackov | 1 | -0/+17 | |
| 2022-11-29 | Fix backlink logic for target groups | Boris Kolpackov | 1 | -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-28 | Add ability to disable diagnostics buffering (--no-diag-buffer) | Boris Kolpackov | 1 | -0/+5 | |
| 2022-10-19 | Add support for post hoc prerequisites | Boris Kolpackov | 1 | -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-13 | Fix couple of corner cases in public/private variable model | Boris Kolpackov | 1 | -43/+47 | |
| 2022-10-13 | Switch to public/private variables model | Boris Kolpackov | 1 | -7/+6 | |
| Now unqualified variables are project-private and can be typified. | |||||
| 2022-10-11 | Factor variable patterns out of variable_pool into separate variable_patterns | Boris Kolpackov | 1 | -1/+2 | |
| We have patterns only for the public variables pool. | |||||
| 2022-10-10 | Preparatory work for public/private variable distinction | Boris Kolpackov | 1 | -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-12 | Add note on backlink=overwrite mode | Boris Kolpackov | 1 | -1/+23 | |
| 2022-06-29 | Rework pkg-config variable naming, use build2.metadata as general indicator | Boris Kolpackov | 1 | -4/+6 | |
| 2022-06-21 | Add --trace-{match,execute} options | Boris Kolpackov | 1 | -0/+11 | |
| These options can be used to understand which dependency chain causes matching or execution of a particular target. | |||||
| 2022-05-23 | Cache build.host value in context | Boris Kolpackov | 1 | -0/+4 | |
| 2022-04-20 | Add import cache | Boris Kolpackov | 1 | -0/+20 | |
| 2022-04-15 | Omit unnecessary clearing of cached base_scope values | Boris Kolpackov | 1 | -1/+6 | |
| 2022-04-13 | Cache target base scope lookups | Boris Kolpackov | 1 | -2/+8 | |
| 2022-04-08 | Fix race in phase lock contention counting | Boris Kolpackov | 1 | -1/+2 | |
| 2022-04-08 | Add phase switch contention to build statistics | Boris Kolpackov | 1 | -1/+6 | |
| 2022-03-08 | Add update=execute special value for cases where it's not default | Boris Kolpackov | 1 | -2/+4 | |
| 2022-03-07 | Fix operation-specific variables logic for inner/outer operations | Boris Kolpackov | 1 | -1/+5 | |
| 2022-03-02 | Add update operation-specific variable with unmatch|match additional values | Boris Kolpackov | 1 | -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-14 | Factor reusable code to contex::enter_project_overrides() | Boris Kolpackov | 1 | -0/+7 | |
| 2022-02-10 | Make few global types separately constructible/initializable | Boris Kolpackov | 1 | -2/+12 | |
| 2021-10-07 | Allow forcing installation of exe{} prerequisites of file targets | Boris Kolpackov | 1 | -1/+1 | |
| This can be achieved with prerequisite-specific install=true, for example: exe{foo}: exe{bar}: install = true # foo runs bar | |||||
| 2021-09-20 | Add support for disabling clean through target-prerequisite relationship | Boris Kolpackov | 1 | -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-12 | Deal with helper thread starvation during phase switching | Boris Kolpackov | 1 | -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-12 | Keep phase locked while working own queue | Boris Kolpackov | 1 | -2/+6 | |
| 2021-05-07 | Various improvements and clarifications in metadata handling | Boris Kolpackov | 1 | -3/+4 | |
| 2021-03-16 | Define intermediate build results file cache interface | Boris Kolpackov | 1 | -0/+3 | |
| 2021-01-15 | Disable questionable unused functionality | Boris Kolpackov | 1 | -1/+3 | |
| 2020-11-11 | Add context::current_action() | Boris Kolpackov | 1 | -1/+9 | |
| 2020-09-22 | Add ability to skip external modules during bootstrap (--no-external-modules) | Boris Kolpackov | 1 | -0/+5 | |
| 2020-08-16 | Add support for post-configure and pre-disfigure hooks | Boris Kolpackov | 1 | -0/+10 | |
| 2020-06-09 | Make metadata variable prefix mandatory | Boris Kolpackov | 1 | -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-02 | Add process_path_ex with program stable name and checksum | Boris Kolpackov | 1 | -0/+2 | |
| 2020-06-01 | Extend target metadata to include variable prefix, stable name | Boris Kolpackov | 1 | -3/+25 | |
| 2020-05-27 | Initial support for ad hoc recipes (still work in progress) | Boris Kolpackov | 1 | -5/+14 | |
| 2020-04-27 | Rework tool importation along with cli module | Boris Kolpackov | 1 | -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-13 | Cleanup and make config/utility.?xx part of build system core | Boris Kolpackov | 1 | -12/+0 | |
| 2020-02-11 | Add match_only flag to context | Boris Kolpackov | 1 | -0/+5 | |
| 2020-02-07 | Drop copyright notice from source code | Karen Arutyunov | 1 | -1/+0 | |
| 2019-10-29 | Add forward declaration header for build state types | Boris Kolpackov | 1 | -20/+1 | |
| 2019-10-25 | Fix inconsistent loaded_modules_lock declaration | Boris Kolpackov | 1 | -1/+1 | |
| 2019-10-25 | Expand context comment | Boris Kolpackov | 1 | -2/+13 | |
| 2019-10-23 | Un-tune scheduler when building build system modules | Boris Kolpackov | 1 | -0/+3 | |
| 2019-10-22 | Implement loaded_modules state locking | Boris Kolpackov | 1 | -1/+13 | |
| This would be necessary if someone runs two parallel top-level contexts. | |||||
| 2019-10-22 | Rename global_mutex_shards to global_mutexes | Boris Kolpackov | 1 | -4/+9 | |
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |