Age | Commit message (Collapse) | Author | Files | Lines |
|
This just keep breaking (this time for exe{}: in{} match during distribution).
So we assume rules will assign the target platform extension if necessary
and if not, then we default to no extension (e.g., a shell script).
|
|
|
|
Significantly, the version::in_rule rule now track changes to the substitution
values.
|
|
|
|
|
|
Given test.in containing something along these lines:
foo = $foo$
Now we can do:
using in
file{test}: in{test.in}
file{test}: foo = FOO
The alternative variable substitution symbol can be specified with the
in.symbol variable and lax (instead of the default strict) mode with
in.substitution. For example:
file{test}: in.symbol = '@'
file{test}: in.substitution = lax
|