aboutsummaryrefslogtreecommitdiff
path: root/tests/recipe/buildscript/testscript
AgeCommit message (Collapse)AuthorFilesLines
2022-10-21Change attribute syntax in script to come after variable in set and for (set ↵Karen Arutyunov1-19/+52
x [...], for x [...])
2022-10-18Fix unexpected 'unterminated double-quoted sequence' script errorKaren Arutyunov1-0/+42
2022-10-18Invent diag preamble for buildscriptKaren Arutyunov1-0/+19
2022-10-13Fix script 'for' loop testsKaren Arutyunov1-1/+1
2022-10-13Add support for 'for' loop second (... | for x) and third (for x <...) forms ↵Karen Arutyunov1-14/+679
in script
2022-09-28Add support for 'for' loop first form (for x:...) in scriptKaren Arutyunov1-0/+122
2022-09-28Add support for 'while' loop in scriptKaren Arutyunov1-14/+40
2022-09-19Allow computed variables in depdb preamble similar to impure functionsBoris Kolpackov1-5/+27
2022-07-07Use new cmdline type for canned command lines in {Build,Test}scriptBoris Kolpackov1-0/+24
2022-01-18Add dynamic prerequisites to $< unless --adhoc is specifiedBoris Kolpackov1-57/+152
Also add a few tests for depdb-dyndep.
2021-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov1-0/+20
An ad hoc pattern rule consists of a pattern that mimics a dependency declaration followed by one or more recipes. For example: exe{~'/(.*)/'}: cxx{~'/\1/'} {{ $cxx.path -o $path($>) $path($<[0]) }} If a pattern matches a dependency declaration of a target, then the recipe is used to perform the corresponding operation on this target. For example, the following dependency declaration matches the above pattern which means the rule's recipe will be used to update this target: exe{hello}: cxx{hello} While the following declarations do not match the above pattern: exe{hello}: c{hello} # Type mismatch. exe{hello}: cxx{howdy} # Name mismatch. On the left hand side of `:` in the pattern we can have a single target or an ad hoc target group. The single target or the first (primary) ad hoc group member must be a regex pattern (~). The rest of the ad hoc group members can be patterns or substitutions (^). For example: <exe{~'/(.*)/'} file{^'/\1.map/'}>: cxx{~'/\1/'} {{ $cxx.path -o $path($>[0]) "-Wl,-Map=$path($>[1])" $path($<[0]) }} On the left hand side of `:` in the pattern we have prerequisites which can be patterns, substitutions, or non-patterns. For example: <exe{~'/(.*)/'} file{^'/\1.map/'}>: cxx{~'/\1/'} hxx{^'/\1/'} hxx{common} {{ $cxx.path -o $path($>[0]) "-Wl,-Map=$path($>[1])" $path($<[0]) }} Substitutions on the left hand side of `:` and substitutions and non-patterns on the right hand side are added to the dependency declaration. For example, given the above rule and dependency declaration, the effective dependency is going to be: <exe{hello} file{hello.map>: cxx{hello} hxx{hello} hxx{common}
2021-04-21Add buildscript depdb builtin 'env' commandKaren Arutyunov1-0/+62
2020-12-11Add export script pseudo-builtinKaren Arutyunov1-2/+35
2020-12-08Add support for config.test.runnerKaren Arutyunov1-2/+49
2020-12-08Fix buildscript assertion failure on redirecting command stderr to stdoutKaren Arutyunov1-0/+23
2020-12-02Add support for buildscript depdb preambleKaren Arutyunov1-16/+301
2020-11-19Remove target files on ad hoc rule update buildscript errorKaren Arutyunov1-13/+60
2020-11-06Add support for test timeoutsKaren Arutyunov1-0/+120
2020-08-03Fix buildscript diagnostics so diff output is always in unified formatKaren Arutyunov1-0/+22
Also make sure diff refers program stdout as 'stdout' rather than '-' in the test rule diagnostics.
2020-06-11Add tests for ad hoc C++ recipesBoris Kolpackov1-9/+0
2020-06-08Add buildscript recipe testsKaren Arutyunov1-0/+96