summaryrefslogtreecommitdiffstats
path: root/Tests/LinkFlags/CMakeLists.txt
Commit message (Collapse)AuthorAgeFilesLines
* Tests: Bump CMake minimum required in tests to 3.5Brad King2023-03-011-1/+1
| | | | | | | | | | | | | | | | | | | CMake 3.27 deprecates compatibility with CMake < 3.5. Update tests that do not cover older interfaces to avoid the deprecation warning. Follow the pattern from: * commit 7b07ccdd2b (Tests/*Only: Update cmake_minimum_required versions, 2020-06-15, v3.19.0-rc1~629^2~1) * commit 72e7c45e98 (Tests: Bump CMake minimum required in tests to 2.8.12, 2020-12-22, v3.20.0-rc1~224^2) * commit f6b4db365a (Tests: bump cmake_minimum_required version to 2.8.12, 2021-04-04, v3.21.0-rc1~372^2) Also remove explicit `cmake_policy` settings made redundant by the version.
* Tests: Move LINK_FLAGS case from COnly to LinkFlags testBrad King2023-02-031-0/+5
| | | | | | Move the case added by commit 246e964180 (BUG: fix for bug 5455, handle nodefaultlib with more than one lib, 2007-12-06, v2.6.0~751) to a more sensible test.
* Tests: Bump CMake minimum required in tests to 2.8.12Chuck Atkins2020-12-231-1/+1
| | | | | | | Since 3.19, CMake generates a deprecation warning when using a minimum version less than 2.8.12. This eliminates those warnings generated during tests, which are typically hidden from the user and developer but are being generated nonetheless.
* Add additonal tests for the linker flagsPatrick Gansterer2013-07-311-0/+9
| | | | | 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-031-2/+2
| | | | | | | | 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-281-0/+24
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.