summaryrefslogtreecommitdiffstats
path: root/Tests/LinkFlags
Commit message (Collapse)AuthorAgeFilesLines
* Revise C++ coding style using clang-formatKitware Robot2016-05-163-5/+14
| | | | | | | | | | | | | 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.
* Add additonal tests for the linker flagsPatrick Gansterer2013-07-313-0/+31
| | | | | Extend Tests/LinkFlags to test libraries of the type MODULE and the content of the CMAKE_*_LINKER_FLAGS_* variables.
* Intel-specific workaround for LinkFlags testsBrad King2010-06-033-2/+13
| | | | | | | | The Intel C compiler for Linux does not seem to reject any bad flags or object files on its link lines. Work around the problem by using a preprocessor #error directive to ensure that BADFLAG appears in the build output. This does not really achieve the purpose of the tests but it allows them to pass.
* Borland-specific bad flag for LinkFlags testsBrad King2010-06-021-6/+9
| | | | | | The Borland librarian actually creates a BADFLAG.obj when the object is missing the first time! This causes later tests to not reject it. Instead use a Borland-specific variation on the flag.
* Better "bad" flag in LinkFlags testBrad King2010-06-011-6/+7
| | | | | The Intel C Compiler for Linux ignores _BADFLAG_ when linking! Use a flag that looks like a missing object file to ensure its rejection.
* Test LINK_FLAGS and STATIC_LIBRARY_FLAGS (#10768)Brad King2010-05-283-0/+26
Add a LinkFlags test series to check that these properties work. Since no link flag is accepted everywhere we test for presence of flags by adding a bad flag and looking for the complaint in the test output.