diff options
author | Boris Kolpackov <boris@codesynthesis.com> | 2022-09-05 13:33:44 +0200 |
---|---|---|
committer | Boris Kolpackov <boris@codesynthesis.com> | 2022-09-05 13:40:04 +0200 |
commit | 52296a1e3e57bdfa80003f37b63f4f263734e2c0 (patch) | |
tree | 3b6eceff0d0f8d2af60e31b1772cf39407222c8b /libbuild2/script/lexer.test.cxx | |
parent | cd6b44707cefff2be90343c8c1f7e6751d5f5d01 (diff) |
Allow empty prerequisites in prerequisite-specific variable assignment/block
The old semantics was not very consistent, consider:
exe{foo}: cxx{$empty} # Ok.
exe{foo}: cxx{$empty}: include = false # Not ok?
So now both are ok, as well as the block variant:
exe{foo}: cxx{$empty}:
{
include = false
}
Note that the empty prerequisite list in the dependency chain is still an
error:
./: exe{$empty}: cxx{foo} # Error.
Note also that the syntactically-empty prerequisite list was and still is
an error:
exe{foo}: : include = false # Error.
Diffstat (limited to 'libbuild2/script/lexer.test.cxx')
0 files changed, 0 insertions, 0 deletions