| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2022-04-06 | Add support for rule hints | Boris Kolpackov | 1 | -1/+1 | |
| 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-02-11 | Remove unnecessary header inclusions | Boris Kolpackov | 1 | -0/+1 | |
| 2021-09-28 | Adapt to libbutl headers extension change from .mxx to .hxx | Karen Arutyunov | 1 | -1/+1 | |
| 2021-08-04 | Take into account file-base'ness in ad hoc buildscript recipes | Boris Kolpackov | 1 | -1/+1 | |
| 2021-06-08 | Redo low verbosity diagnostic deduction to use scope instead of target | Boris Kolpackov | 1 | -1/+1 | |
| 2021-06-08 | Implement ad hoc regex pattern rule support | Boris Kolpackov | 1 | -9/+16 | |
| 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 | 1 | -1/+1 | |
| 2021-05-13 | Don't both mark the scheduler queue and enter sub-phase | Boris Kolpackov | 1 | -9/+1 | |
| 2021-05-12 | Deal with helper thread starvation during phase switching | Boris Kolpackov | 1 | -0/+4 | |
| 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-04 | Replace int_ with intf_ and imp_ with impl_ in names | Boris Kolpackov | 1 | -2/+2 | |
| 2021-04-02 | Add support for propagating project environment | Boris Kolpackov | 1 | -1/+3 | |
| 2021-01-13 | Make sure we don't work any existing tasks when building in module context | Boris Kolpackov | 1 | -0/+5 | |
| 2020-12-02 | Add support for buildscript depdb preamble | Karen Arutyunov | 1 | -1/+2 | |
| 2020-10-20 | Add operation callback for adhoc rule match and apply | Boris Kolpackov | 1 | -5/+5 | |
| 2020-07-12 | Rename rule-adhoc-* to adhoc-rule-* | Boris Kolpackov | 1 | -0/+665 | |
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |