| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2021-09-24 | Fortify tests against NDEBUG | Karen Arutyunov | 2 | -2/+6 | |
| 2021-08-04 | Take into account file-base'ness in ad hoc buildscript recipes | Boris Kolpackov | 3 | -7/+17 | |
| 2021-06-08 | Redo low verbosity diagnostic deduction to use scope instead of target | Boris Kolpackov | 3 | -22/+26 | |
| 2021-06-08 | Implement ad hoc regex pattern rule support | Boris Kolpackov | 3 | -4/+6 | |
| 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-06-08 | Only pass target to recipe_text() if recipe is not shared | Boris Kolpackov | 3 | -12/+19 | |
| 2021-05-28 | Add pattern_mode::ignore and use in appropriate places | Boris Kolpackov | 1 | -3/+3 | |
| 2021-05-28 | Make notion of name pattern explicit, fix various related loose ends | Boris Kolpackov | 1 | -3/+3 | |
| 2021-04-21 | Add buildscript depdb builtin 'env' command | Karen Arutyunov | 2 | -6/+36 | |
| 2021-04-20 | Detect environment changes in ad hoc recipes | Boris Kolpackov | 1 | -1/+1 | |
| 2021-03-18 | Add noop mode to file cache, add --file-cache option to select | Boris Kolpackov | 1 | -1/+1 | |
| 2021-03-16 | Define intermediate build results file cache interface | Boris Kolpackov | 1 | -1/+3 | |
| 2020-12-11 | Prefix pseudo-builtin diagnostincs messages with their names | Karen Arutyunov | 1 | -2/+3 | |
| 2020-12-08 | In update ad hoc recipe buildscripts allow non-pure function calls only in ↵ | Karen Arutyunov | 3 | -2/+100 | |
| depdeb preamble | |||||
| 2020-12-08 | Add support for config.test.runner | Karen Arutyunov | 1 | -0/+10 | |
| 2020-12-02 | Add support for buildscript depdb preamble | Karen Arutyunov | 8 | -126/+555 | |
| 2020-11-06 | Add support for test timeouts | Karen Arutyunov | 2 | -4/+50 | |
| 2020-06-18 | Add env script pseudo-builtin | Karen Arutyunov | 3 | -4/+47 | |
| Also disable C++ recipe tests when cross-testing. | |||||
| 2020-06-18 | Fix untracked variable check in buildscript parser | Karen Arutyunov | 1 | -1/+1 | |
| 2020-06-10 | Handle special variable names in base lexer via mode data | Boris Kolpackov | 2 | -33/+9 | |
| 2020-06-08 | Fix crashing when special builtin appears inside if condition or branch | Karen Arutyunov | 2 | -1/+33 | |
| 2020-06-08 | Fix crashing for buildscript diag line using non-local variable | Karen Arutyunov | 1 | -11/+35 | |
| 2020-06-08 | Add note on why not using rule-specific variables for ad hoc recipes | Boris Kolpackov | 1 | -2/+10 | |
| 2020-06-05 | Add depdb buildscript builtin | Karen Arutyunov | 5 | -53/+163 | |
| 2020-06-05 | Add ability to specify ad hoc recipe actions | Boris Kolpackov | 1 | -1/+1 | |
| We are reusing the buildspec syntax for that. | |||||
| 2020-06-04 | Properly handle diag directive in build script parser | Karen Arutyunov | 5 | -58/+273 | |
| 2020-06-03 | Fix $process.run() to properly handle proces_path_ex | Karen Arutyunov | 1 | -9/+3 | |
| 2020-06-03 | Allow process path values and targets as buildscript program names | Karen Arutyunov | 6 | -23/+471 | |
| Also deduce the recipe name. | |||||
| 2020-06-01 | Fix buildscript unit test to compile | Boris Kolpackov | 1 | -1/+1 | |
| 2020-05-29 | Move low-verbosity command name from adhoc_script_rule to script | Boris Kolpackov | 3 | -2/+11 | |
| 2020-05-27 | Add support for value subscript after expansions | Boris Kolpackov | 1 | -8/+7 | |
| Value subscript is only recognized in evaluation contexts (due to ambiguity with wildcard patterns; consider: $x[123].txt) and should be unseparated from the previous token. For example: x = ($y[1]) x = (($f ? $y : $z)[1]) x = ($identity($y)[$z]) | |||||
| 2020-05-27 | Initial support for ad hoc recipes (still work in progress) | Boris Kolpackov | 30 | -0/+3937 | |
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |