Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2024-01-08 | Improve documentation comment | Boris Kolpackov | 1 | -2/+2 | |
2023-05-29 | Explicit group: syntax parsing | Boris Kolpackov | 1 | -1/+5 | |
2023-04-19 | Fix several issues in build system module importation logicmodule-import | Boris Kolpackov | 1 | -5/+6 | |
2023-04-13 | Various minor generalizations for in-process configure support in bpkg | Boris Kolpackov | 1 | -1/+1 | |
2022-11-29 | Move buildfiles to root_extra, use vector instead of unordered_set | Boris Kolpackov | 1 | -9/+19 | |
2022-10-13 | Work around Clang 6, 7 codegen issues | Boris Kolpackov | 1 | -2/+3 | |
2022-10-13 | Switch to public/private variables model | Boris Kolpackov | 1 | -21/+51 | |
Now unqualified variables are project-private and can be typified. | |||||
2022-10-10 | Preparatory work for public/private variable distinction | Boris Kolpackov | 1 | -1/+14 | |
We still always use the public var_pool from context but where required, all access now goes through scope::var_pool(). | |||||
2022-10-10 | Use term shared instead of global for scope, var pool, etc | Boris Kolpackov | 1 | -2/+2 | |
2022-06-17 | Add ability to ignore subprojects in create_bootstrap_outer() | Boris Kolpackov | 1 | -1/+1 | |
2022-04-20 | Add explicit flag to more efficiently avoid repeated load_root() calls | Boris Kolpackov | 1 | -1/+2 | |
2022-04-19 | Switch to using std::function for target::data_pad | Boris Kolpackov | 1 | -0/+7 | |
2022-04-15 | Omit unnecessary clearing of cached base_scope values | Boris Kolpackov | 1 | -1/+1 | |
2022-04-06 | Add support for rule hints | Boris Kolpackov | 1 | -3/+3 | |
A rule hint is a target attribute, for example: [rule_hint=cxx] exe{hello}: c{hello} Rule hints can be used to resolve ambiguity when multiple rules match the same target as well as to override an unambiguous match. | |||||
2022-03-11 | Add JSON format support for --structured-result option and info meta operation | Karen Arutyunov | 1 | -1/+5 | |
2022-02-10 | Reorder inline function definition to help with MinGW GCC symbol export | Boris Kolpackov | 1 | -28/+1 | |
2022-02-09 | Fix issue with implicit size_t to meta_operation_id conversion | Boris Kolpackov | 1 | -9/+13 | |
2022-02-07 | Add support for meta-operation wildcard in scope::insert_rule() | Boris Kolpackov | 1 | -1/+25 | |
2021-09-29 | Add notion of bundle amalgamation scope | Boris Kolpackov | 1 | -0/+9 | |
2021-09-15 | Do variable lookup in ad hoc target groups | Boris Kolpackov | 1 | -1/+2 | |
2021-06-08 | Implement ad hoc regex pattern rule support | Boris Kolpackov | 1 | -8/+12 | |
An ad hoc pattern rule consists of a pattern that mimics a dependency declaration followed by one or more recipes. For example: exe{~'/(.*)/'}: cxx{~'/\1/'} {{ $cxx.path -o $path($>) $path($<[0]) }} If a pattern matches a dependency declaration of a target, then the recipe is used to perform the corresponding operation on this target. For example, the following dependency declaration matches the above pattern which means the rule's recipe will be used to update this target: exe{hello}: cxx{hello} While the following declarations do not match the above pattern: exe{hello}: c{hello} # Type mismatch. exe{hello}: cxx{howdy} # Name mismatch. On the left hand side of `:` in the pattern we can have a single target or an ad hoc target group. The single target or the first (primary) ad hoc group member must be a regex pattern (~). The rest of the ad hoc group members can be patterns or substitutions (^). For example: <exe{~'/(.*)/'} file{^'/\1.map/'}>: cxx{~'/\1/'} {{ $cxx.path -o $path($>[0]) "-Wl,-Map=$path($>[1])" $path($<[0]) }} On the left hand side of `:` in the pattern we have prerequisites which can be patterns, substitutions, or non-patterns. For example: <exe{~'/(.*)/'} file{^'/\1.map/'}>: cxx{~'/\1/'} hxx{^'/\1/'} hxx{common} {{ $cxx.path -o $path($>[0]) "-Wl,-Map=$path($>[1])" $path($<[0]) }} Substitutions on the left hand side of `:` and substitutions and non-patterns on the right hand side are added to the dependency declaration. For example, given the above rule and dependency declaration, the effective dependency is going to be: <exe{hello} file{hello.map>: cxx{hello} hxx{hello} hxx{common} | |||||
2021-05-28 | Tie loose ends in target type/pattern-specific matching | Boris Kolpackov | 1 | -13/+25 | |
2021-05-28 | Make notion of name pattern explicit, fix various related loose ends | Boris Kolpackov | 1 | -0/+4 | |
2021-04-22 | Incorporate project environment checksum into cc::compiler_info cache key | Boris Kolpackov | 1 | -0/+6 | |
2021-04-02 | Add support for propagating project environment | Boris Kolpackov | 1 | -0/+30 | |
2021-03-19 | Redo entering of src directories into scope_map | Boris Kolpackov | 1 | -40/+55 | |
2021-02-08 | Enter scope src directories into scope map | Boris Kolpackov | 1 | -9/+48 | |
2021-02-03 | Propagate relevant options/prerequisites to header unit sidebuilds | Boris Kolpackov | 1 | -3/+11 | |
2021-01-30 | Add std::{map, multimap} to types.hxx | Boris Kolpackov | 1 | -4/+2 | |
Seeing that std::map is becoming a common Buildfile variable type. | |||||
2020-11-12 | Assign fixed extensions to wasm{} and pdb{} target types | Boris Kolpackov | 1 | -0/+5 | |
2020-07-12 | Cache subprojects variable value in scope::root_extra | Boris Kolpackov | 1 | -0/+11 | |
2020-07-09 | Get rid of no longer needed friend | Boris Kolpackov | 1 | -4/+0 | |
2020-07-02 | Cache project name in root_extra | Boris Kolpackov | 1 | -0/+12 | |
2020-06-09 | Move recipe build directory to build/build/recipes/ | Boris Kolpackov | 1 | -2/+3 | |
Our new scheme is to have any "out" content in a subdirectory called build/ (build/build/ for the build system core, build/<module>/build/ for modules). This way we can ignore them in .gitignore with a generic entry. | |||||
2020-05-27 | Amalgamation cutoff support | Boris Kolpackov | 1 | -5/+21 | |
Now a project that disables amalgamation will not logically "see" an outer project even if it's physically inside its scope. | |||||
2020-04-27 | Rework tool importation along with cli module | Boris Kolpackov | 1 | -0/+21 | |
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-27 | Require explicit variable type in scope::{assign,append}() | Boris Kolpackov | 1 | -26/+39 | |
2020-03-31 | Switch to project variable visibility by default | Boris Kolpackov | 1 | -1/+19 | |
2020-03-27 | Implement project configuration reporting, similar to build system modules | Boris Kolpackov | 1 | -0/+6 | |
2020-03-20 | Initial implementation of config directive for project-specific configuration | Boris Kolpackov | 1 | -6/+6 | |
2020-03-19 | Tweak lookup_config() semantics some more | Boris Kolpackov | 1 | -2/+22 | |
2020-03-17 | Rename all find*(variable) to lookup*(variable) | Boris Kolpackov | 1 | -24/+26 | |
Now we consistently use term "lookup" for variable value lookup. At some point we should also rename type lookup to binding and get rid of all the lookup_type aliases. | |||||
2020-02-07 | Drop copyright notice from source code | Karen Arutyunov | 1 | -1/+0 | |
2020-01-29 | Rename module_base to module, redo module boot/init argument passing | Boris Kolpackov | 1 | -1/+1 | |
2020-01-28 | Use scope::var_pool() | Boris Kolpackov | 1 | -2/+2 | |
2020-01-27 | See through lib{} group during dist | Boris Kolpackov | 1 | -0/+6 | |
2020-01-27 | Add scope::{insert_rule,var_pool}() convenience functions | Boris Kolpackov | 1 | -2/+32 | |
2019-11-14 | Make use of butl::to_stream(ostream, path, bool) | Karen Arutyunov | 1 | -1/+3 | |
2019-11-04 | Add $config.export() function | Boris Kolpackov | 1 | -4/+4 | |
This is similar to the config.export variable functionality except it can be called from within buildfiles. Note that this function can only be used during configure unless the config module creation was forced for other meta-operations with config.module=true in bootstrap.build. | |||||
2019-10-29 | Add forward declaration header for build state types | Boris Kolpackov | 1 | -0/+1 | |