summaryrefslogtreecommitdiffstats
path: root/Tests/PerConfig
Commit message (Collapse)AuthorAgeFilesLines
* Revise C++ coding style using clang-format-6.0Kitware Robot2018-06-011-6/+6
| | | | | | | | | | | | Run the `clang-format.bash` script to update all our C and C++ code to a new style defined by `.clang-format`. Use `clang-format` version 6.0. * If you reached this commit for a line in `git blame`, re-run the blame operation starting at the parent of this commit to see older history for the content. * See the parent commit for instructions to rebase a change across this style transition commit.
* Revise C++ coding style using clang-formatKitware Robot2016-05-161-6/+6
| | | | | | | | | | | | | Run the `Utilities/Scripts/clang-format.bash` script to update all our C++ code to a new style defined by `.clang-format`. Use `clang-format` version 3.8. * If you reached this commit for a line in `git blame`, re-run the blame operation starting at the parent of this commit to see older history for the content. * See the parent commit for instructions to rebase a change across this style transition commit.
* Use a more reliable regex for extracting binary INFO stringsChuck Atkins2014-09-031-1/+1
| | | | | | | A few different regular expressions were being used in various places to extract info strings from binaries. This uses a consistent regex amongst all of them now. This also fixes the broken ABI detection for Cray compilers.
* Remove .* expressions from beginning and end of MATCHES regexsRolf Eike Beer2014-04-141-1/+1
| | | | | | | | | All these expressions work the same: "foo" ".*foo.*" "^.*foo.*$" This assumes that the "Intel*" expressions were meant to be "Intel.*".
* Convert CMake-language commands to lower caseKitware Robot2012-08-131-18/+18
| | | | | | | | | | | | | | | | | Ancient CMake versions required upper-case commands. Later command names became case-insensitive. Now the preferred style is lower-case. Run the following shell code: cmake --help-command-list | grep -v "cmake version" | while read c; do echo 's/\b'"$(echo $c | tr '[:lower:]' '[:upper:]')"'\(\s*\)(/'"$c"'\1(/g' done >convert.sed && git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' | egrep -z -v '^(Utilities/cm|Source/kwsys/)' | xargs -0 sed -i -f convert.sed && rm convert.sed
* 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.
generated by cgit v0.12 at 2024-11-12 02:08:03 (GMT)