CMake.git - CMake is a cross-platform, open-source build system generator.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Tests: Move LINK_FLAGS case from COnly to LinkFlags test	Brad King	2023-02-03	1	-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.12	Chuck Atkins	2020-12-23	1	-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.
*	Revise C++ coding style using clang-format-6.0	Kitware Robot	2018-06-01	2	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \|	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-format	Kitware Robot	2016-05-16	3	-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 flags	Patrick Gansterer	2013-07-31	3	-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 tests	Brad King	2010-06-03	3	-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 tests	Brad King	2010-06-02	1	-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 test	Brad King	2010-06-01	1	-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 King	2010-05-28	3	-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.