path: root/tests/directive
AgeCommit message (Collapse)AuthorFilesLines
2018-11-21Add support for target and prerequisite specific variable blocksBoris Kolpackov1-1/+1
For example, now instead of: lib{foo}: cxx.loptions += -static lib{foo}: cxx.libs += -lpthread We can write: lib{foo}: { cxx.loptions += -static cxx.libs += -lpthread } The same works for prerequisites as well as target type/patterns. For example: exe{*.test}: { test = true install = false }
2018-11-14Tweak assert directive diagnosticsBoris Kolpackov1-1/+1
2018-09-04Rename .test/test{} to .testscript/testscript{}Boris Kolpackov3-5/+5
2018-05-19Update copyright yearKaren Arutyunov3-3/+3
2018-04-27Redo run directive diagnostics not to rely on invalid pathsBoris Kolpackov1-2/+3
2018-04-26Fix bug in directive/run testBoris Kolpackov1-4/+4
2018-04-26Implement run buildfile directiveBoris Kolpackov1-0/+36
Now we can do: run echo 'foo = bar' print $foo
2017-07-12Make use of wildcards in buildfilesKaren Arutyunov1-1/+1
2017-01-05Update copyright yearBoris Kolpackov2-2/+2
2016-12-16Convert tests/ to subproject, initial work on cross-testing supportBoris Kolpackov1-1/+1
2016-12-05Use new convert() in if-else, assert parsingBoris Kolpackov1-1/+1
2016-12-01Organize tests/, factor common testscript fragmentsBoris Kolpackov3-15/+2
2016-11-23Implement assert directiveBoris Kolpackov3-0/+46
The grammar is as follows: assert <expression> [<description>] assert! <expression> [<description>] The expression must evaluate to 'true' or 'false', just like in if-else.
2015-12-03Implement new potential directive keyword testBoris Kolpackov3-12/+0
Now we can use directive names as variables and targets type, for example: print = foo # variable print{foo}: # target
2015-09-09Add support for quoting directive namesBoris Kolpackov3-0/+12
Now only unquoted, literal names are recognized as directives, for example: 'print' = abc print $print