diff options
author | Boris Kolpackov <boris@codesynthesis.com> | 2024-02-12 09:34:50 +0200 |
---|---|---|
committer | Boris Kolpackov <boris@codesynthesis.com> | 2024-02-12 09:34:50 +0200 |
commit | 20e49b4e63779abc0e25bec4c74399a83ec8a83c (patch) | |
tree | 9f2f01ff0b6a40142fa8ee04a1a394c5b98c9a57 /libbuild2/build/script/parser+pre-parse.test.testscript | |
parent | f0cfe78cb306532518d42e3d2b8e59405d006717 (diff) |
Add ability to specify recipes in separate files
This can now be achieved with the new `recipe` directive:
recipe <language> <file>
Note that similar to the use of if-else and switch directives with recipes,
this directive requires explicit % recipe header. For example, instead of:
file{foo.output}:
{{
echo 'hello' >$path($>)
}}
We can now write:
file{foo.output}:
%
recipe buildscript hello.buildscript
With hello.buildscript containing:
echo 'hello' >$path($>)
Similarly, for C++ recipes (this time for a pattern), instead of:
[rule_name=hello] file{~'/(.+)\.output/'}:
% update clean
{{ c++ 1 --
--
...
}}
We can now write:
[rule_name=hello] file{~'/(.+)\.output/'}:
% update clean
recipe c++ hello.cxx
With hello.cxx containing:
// c++ 1 --
--
...
Relative <file> paths are resolved using the buildfile directory that contains
the `recipe` directive as a base.
Note also that this mechanism can be used in exported buildfiles with recipe
files placed into build/export/ together with buildfiles.
Diffstat (limited to 'libbuild2/build/script/parser+pre-parse.test.testscript')
0 files changed, 0 insertions, 0 deletions