| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2022-01-18 | Add dynamic prerequisites to $< unless --adhoc is specified | Boris Kolpackov | 1 | -57/+152 | |
| Also add a few tests for depdb-dyndep. | |||||
| 2021-06-09 | Fix cxx pattern rule test | Boris Kolpackov | 1 | -6/+7 | |
| 2021-06-08 | Implement ad hoc regex pattern rule support | Boris Kolpackov | 2 | -0/+59 | |
| 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-04-21 | Add buildscript depdb builtin 'env' command | Karen Arutyunov | 1 | -0/+62 | |
| 2020-12-14 | Make use of export testscript builtin | Karen Arutyunov | 1 | -5/+7 | |
| 2020-12-11 | Add export script pseudo-builtin | Karen Arutyunov | 1 | -2/+35 | |
| 2020-12-08 | Add support for config.test.runner | Karen Arutyunov | 1 | -2/+49 | |
| 2020-12-08 | Fix buildscript assertion failure on redirecting command stderr to stdout | Karen Arutyunov | 1 | -0/+23 | |
| 2020-12-02 | Add support for buildscript depdb preamble | Karen Arutyunov | 1 | -16/+301 | |
| 2020-11-19 | Remove target files on ad hoc rule update buildscript error | Karen Arutyunov | 1 | -13/+60 | |
| 2020-11-06 | Add support for test timeouts | Karen Arutyunov | 1 | -0/+120 | |
| 2020-08-03 | Fix buildscript diagnostics so diff output is always in unified format | Karen Arutyunov | 1 | -0/+22 | |
| Also make sure diff refers program stdout as 'stdout' rather than '-' in the test rule diagnostics. | |||||
| 2020-06-18 | Add env script pseudo-builtin | Karen Arutyunov | 1 | -134/+135 | |
| Also disable C++ recipe tests when cross-testing. | |||||
| 2020-06-16 | Add metadata for exe{b}, including whether it is statically-linked | Boris Kolpackov | 1 | -0/+4 | |
| Use this information to omit ad hoc C++ recipe tests is testing statically- linked build system. | |||||
| 2020-06-12 | Fix invalid regex in C++ recipe tests | Boris Kolpackov | 1 | -2/+2 | |
| 2020-06-11 | Add tests for ad hoc C++ recipes | Boris Kolpackov | 3 | -9/+168 | |
| 2020-06-08 | Add buildscript recipe tests | Karen Arutyunov | 2 | -0/+100 | |
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |