aboutsummaryrefslogtreecommitdiff
path: root/tests/variable/prerequisite-specific/testscript
AgeCommit message (Collapse)AuthorFilesLines
2018-11-21Add support for target and prerequisite specific variable blocksBoris Kolpackov1-0/+52
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-16Implement support for dependency chainsBoris Kolpackov1-4/+9
Now instead of: ./: exe{foo} exe{foo}: cxx{*} We can write: ./: exe{foo}: cxx{*} Or even: ./: exe{foo}: libue{foo}: cxx{*} This can be combined with prerequisite-specific variables (which naturally only apply to the last set of prerequisites in the chain): ./: exe{foo}: libue{foo}: bin.whole = false
2018-09-04Rename .test/test{} to .testscript/testscript{}Boris Kolpackov1-1/+1
2018-05-19Update copyright yearKaren Arutyunov1-1/+1
2017-12-16Redo string/stream representation of dir{} name/targetBoris Kolpackov1-8/+8
Now instead of: dir{foo/bar/} We get: foo/dir{bar/} Which feels more consistent with how we print other names/targets. That is, "directory bar/ in directory foo/" similar how foo/exe{bar} is "executable bar in directory foo/".
2017-11-20Add test for prerequisite-specific variablesBoris Kolpackov1-0/+71