| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2022-12-14 | Handle NULL values in $string() and $concat() functions | Boris Kolpackov | 1 | -1/+2 | |
| This is relied upon by the parser to provide conversion/concatenation semantics consistent with untyped values. Note that we handle NULL values only for types that have empty representation. | |||||
| 2022-12-12 | Adapt to dir_iterator API change | Karen Arutyunov | 1 | -1/+14 | |
| 2022-12-02 | Fail if scope or target qualification in variable expansion is unknown | Boris Kolpackov | 1 | -29/+69 | |
| There are three options here: we can "fall through" to an outer scope (there is always the global scope backstop; this is the old semantics, sort of), we can return NULL straight away, or we can fail. It feels like in most cases unknown scope or target is a mistake and doing anything other than failing is just making things harder to debug. | |||||
| 2022-11-29 | Move buildfiles to root_extra, use vector instead of unordered_set | Boris Kolpackov | 1 | -1/+3 | |
| 2022-11-29 | Improve diagnostics for value subscript out of evaluation context | Boris Kolpackov | 1 | -2/+21 | |
| 2022-11-23 | Rework diag_buffer interface to facilitate correct destruction order | Boris Kolpackov | 1 | -1/+1 | |
| 2022-11-08 | Make process exit diagnostics consistent | Boris Kolpackov | 1 | -1/+1 | |
| In particular, we now always print error message on non-0 exit except in cases where such exit is ignored. | |||||
| 2022-11-08 | More work on child process diagnostics buffering | Boris Kolpackov | 1 | -2/+5 | |
| 2022-10-27 | Suppress (potential) bogus GCC 12 -Wrestrict warnings | Boris Kolpackov | 1 | -1/+1 | |
| 2022-10-25 | Allow concatenation of path/dir_path type to be a path pattern | Karen Arutyunov | 1 | -6/+49 | |
| 2022-10-24 | Allow non-parallel absolute src/out to support imported target tagging | Boris Kolpackov | 1 | -11/+11 | |
| Also fix bug in out clearing. | |||||
| 2022-10-21 | Change attribute syntax in script to come after variable in set and for (set ↵ | Karen Arutyunov | 1 | -21/+25 | |
| x [...], for x [...]) | |||||
| 2022-10-20 | Tweak documentation in parser::parse_for() | Karen Arutyunov | 1 | -2/+2 | |
| 2022-10-20 | Add support for for-loop element type | Karen Arutyunov | 1 | -8/+24 | |
| 2022-10-20 | Diagnose incorrect output directory specification | Boris Kolpackov | 1 | -1/+24 | |
| 2022-10-14 | Fix 'for [<attrs>] x: ...' to treat <attrs> as value attributes | Karen Arutyunov | 1 | -12/+0 | |
| 2022-10-13 | Add visibility, overridable variable attributes | Boris Kolpackov | 1 | -11/+70 | |
| 2022-10-13 | Switch to public/private variables model | Boris Kolpackov | 1 | -2/+10 | |
| Now unqualified variables are project-private and can be typified. | |||||
| 2022-10-10 | Preparatory work for public/private variable distinction | Boris Kolpackov | 1 | -5/+4 | |
| We still always use the public var_pool from context but where required, all access now goes through scope::var_pool(). | |||||
| 2022-09-29 | Fix variable append logic in script | Boris Kolpackov | 1 | -0/+12 | |
| 2022-09-28 | Add support for typed value subscript | Boris Kolpackov | 1 | -5/+37 | |
| 2022-09-27 | Fix bug in handling of name patterns with trailing dot | Karen Arutyunov | 1 | -1/+8 | |
| 2022-09-16 | Register fallback dist meta-operation rule for out of project targets | Boris Kolpackov | 1 | -1/+3 | |
| The problematic scenario this fixes is an ad hoc pattern rule (which we register for dist in order to inject any additional sources; see parser.cxx for details) that pulls a tool imported from the system (say /usr/bin/xxd). | |||||
| 2022-09-13 | Fix bug in handling of disabled recipes in ad hoc pattern rules | Boris Kolpackov | 1 | -3/+16 | |
| 2022-09-09 | Evaluate target specific variable assignment/block on ad hoc members | Boris Kolpackov | 1 | -35/+99 | |
| This is in preparation for (again) not treating primary member of an ad hoc group as a group for variable lookup. | |||||
| 2022-09-05 | Allow empty prerequisites in prerequisite-specific variable assignment/block | Boris Kolpackov | 1 | -27/+52 | |
| The old semantics was not very consistent, consider: exe{foo}: cxx{$empty} # Ok. exe{foo}: cxx{$empty}: include = false # Not ok? So now both are ok, as well as the block variant: exe{foo}: cxx{$empty}: { include = false } Note that the empty prerequisite list in the dependency chain is still an error: ./: exe{$empty}: cxx{foo} # Error. Note also that the syntactically-empty prerequisite list was and still is an error: exe{foo}: : include = false # Error. | |||||
| 2022-09-02 | Add missing if! support in recipes | Boris Kolpackov | 1 | -2/+2 | |
| 2022-07-21 | Use bundle scope when deciding whether project is being distributed | Boris Kolpackov | 1 | -2/+3 | |
| 2022-07-21 | Add link to HOWTO entry in conditional dependency declaration warning | Boris Kolpackov | 1 | -1/+3 | |
| 2022-07-21 | Don't issue conditional dependency declaration warning for imported projects | Boris Kolpackov | 1 | -7/+19 | |
| 2022-07-20 | Tweak diagnostics | Boris Kolpackov | 1 | -1/+1 | |
| 2022-07-20 | Adjust conditional dependency declaration warning logic | Boris Kolpackov | 1 | -5/+13 | |
| Now instead of ignoring imported stuff (which turned out to be racy), we only consider conditions up to the include boundary. The thinking here is that an included (but not sourced) buildfile is a standalone entity (e.g., imported project but also could be just a side-included buildfile). Note that unfortunately we will still be issuing warnings in imported projects since there is no straightforward way to know what is being distributed and what is not while parsing. | |||||
| 2022-07-19 | Warn about conditional dependency declarations during distribution | Boris Kolpackov | 1 | -0/+42 | |
| 2022-07-07 | Use new cmdline type for canned command lines in {Build,Test}script | Boris Kolpackov | 1 | -0/+1 | |
| 2022-06-28 | Add support for querying out-qualified target-specific variables | Boris Kolpackov | 1 | -27/+54 | |
| 2022-06-28 | Handle out-qualified prerequisites | Boris Kolpackov | 1 | -6/+20 | |
| 2022-06-28 | Add support for rule-specific import phase 2 | Boris Kolpackov | 1 | -15/+44 | |
| For example: import! [metadata, rule_hint=cxx.link] lib = libhello%lib{hello} | |||||
| 2022-06-21 | Add --trace-{match,execute} options | Boris Kolpackov | 1 | -32/+72 | |
| These options can be used to understand which dependency chain causes matching or execution of a particular target. | |||||
| 2022-06-03 | Reset value::extra on variable_map value change/version increment | Boris Kolpackov | 1 | -1/+1 | |
| The reset on each modification semantics is used to implement the default value distinction as currently done in the config module but later probably will be done for ?= and $origin(). | |||||
| 2022-06-03 | Expose type name to value_type mapping function in parser | Boris Kolpackov | 1 | -4/+4 | |
| 2022-04-08 | Register ad hoc rules for configure in addition to dist | Boris Kolpackov | 1 | -8/+12 | |
| 2022-04-06 | Add support for specifying custom ad hoc pattern rule names | Boris Kolpackov | 1 | -7/+53 | |
| Besides diagnostics, this allows us to use name in the rule hint, for example: [rule_name=hello.link] exe{~'/(.*)/'}: obje{~'/\1/'} {{ $cxx.path -o $path($>) $path($<[0]) }} [rule_hint=hello] exe{hello}: obje{hello} obje{hello}: c{hello-c} | |||||
| 2022-04-06 | Add support for rule hints | Boris Kolpackov | 1 | -14/+115 | |
| 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-23 | Make project configuration variables non-nullable by default | Boris Kolpackov | 1 | -4/+46 | |
| A project configuration variable with the NULL default value is naturally assumed nullable, for example: config [string] config.libhello.fallback_name ?= [null] Otherwise, to make a project configuration nullable we use the `null` variable attribute, for example: config [string, null] config.libhello.fallback_name ?= "World" | |||||
| 2022-02-21 | Ban module names that start with underscore | Boris Kolpackov | 1 | -0/+3 | |
| 2022-02-16 | Invent quoting modes for to_stream(name) | Karen Arutyunov | 1 | -1/+1 | |
| 2022-02-14 | Add parser::parse_eval() public API function | Boris Kolpackov | 1 | -0/+44 | |
| 2022-02-07 | Add support for meta-operation wildcard in scope::insert_rule() | Boris Kolpackov | 1 | -0/+6 | |
| 2022-01-06 | Add depdb-dyndep --update-{include,exclude} options | Boris Kolpackov | 1 | -1/+2 | |
| These options specify prerequisite targets/patterns to include/exclude (from the static prerequisite set) for update during match as part of dynamic dependency extraction (those excluded will be updated during execute). For example: depdb dyndep ... --update-exclude libue{hello-meta} ... depdb dyndep ... --update-exclude libue{*} ... depdb dyndep ... --update-include $moc --update-include hxx{*} ... The order in which these options are specified is significant with the first target/pattern that matches determining the result. If only the --update-include options are specified, then only the explicitly included prerequisites will be updated. Otherwise, all prerequisites that are not explicitly excluded will be updated. If none of these options is specified, then all the static prerequisites are updated during match. Note also that these options do not apply to ad hoc prerequisites which are always updated during match. | |||||
| 2021-12-02 | Automatically register pattern rules for dist meta-operation | Boris Kolpackov | 1 | -4/+28 | |
| We need to do this in order to inject additional pattern prerequisites which may "pull" additional sources into the distribution. | |||||
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |