summaryrefslogtreecommitdiffstats
path: root/Tests/PerConfig
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'resolve/tests-if-CYGWIN'Brad King2010-12-211-1/+1
|\ | | | | | | | | | | 853de2e Merge branch 'custom-command-generator-expressions' into resolve/tests-if-CYGWIN d89e238 Cygwin: Fix tests to check CYGWIN instead of WIN32
| * Merge branch 'custom-command-generator-expressions' into resolve/tests-if-CYGWINBrad King2010-12-171-1/+1
| | | | | | | | | | | | | | | | The tests-if-CYGWIN topic made a change to Tests/Testing/CMakeLists.txt in code that the custom-command-generator-expressions topic moved to the Tests/PerConfig/CMakeLists.txt file. Make the same change to the same content in the new file. (Only a small part of the file moved so rename detection did not do this automatically.)
* | Introduce "generator expression" syntax to custom commands (#11209)Brad King2010-12-152-1/+2
|/ | | | | | | | | Evaluate in the COMMAND arguments of custom commands the generator expression syntax introduced in commit d2e1f2b4 (Introduce "generator expressions" to add_test, 2009-08-11). These expressions have a syntax like $<TARGET_FILE:mytarget> and are evaluated during build system generation. This syntax allows per-configuration target output files to be referenced in custom command lines.
* Factor per-config sample targets out of 'Testing' testBrad King2010-12-156-0/+106
Put the source files, build rules, and test scripts for these targets under Tests/PerConfig and refer to it from Tests/Testing as a subdirectory. The targets and scripts will be useful in other tests.