kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
CMake/Tests/RunCMake/CMakeLists.txt

290 lines
9.5 KiB
CMake
Raw Normal View History

Tests/RunCMake: Move documentation to a README.rst
2014-01-20 22:44:27 +04:00
# See adjacent README.rst for documentation of this test infrastructure.
Add stronger infrastructure for CMake-only tests The CMakeOnly directory added by commit 9a20abf0 (Add infrastructure for CMake-only tests, 2012-01-11) was sufficient only for tests that always run CMake to successfully configure a project. Later commit eeaaffcb (find_package: Test error and warning messages in failure cases, 2012-02-28) added a sample test that covers failure cases. Generalize the above to create new "RunCMake" test infrastructure that can run CMake multiple times for a single project with different variations and check for expected result/stdout/stderr. Allow for both successful and failing CMake project configuration cases. This will be useful to test error messages and failure behavior.
2012-03-10 01:24:43 +04:00
macro(add_RunCMake_test test)
RunCMake: Allow specifying the directory to run tests in.
2015-02-09 10:39:18 +03:00
set(TEST_ARGS ${ARGN})
if ("${ARGV1}" STREQUAL "TEST_DIR")
if ("${ARGV2}" STREQUAL "")
message(FATAL_ERROR "Invalid args")
endif()
set(Test_Dir ${ARGV2})
list(REMOVE_AT TEST_ARGS 0)
list(REMOVE_AT TEST_ARGS 0)
else()
set(Test_Dir ${test})
endif()
Tests: Allow RunCMake tests to pass generator expressions
2014-12-16 00:44:59 +03:00
add_test(NAME RunCMake.${test} COMMAND ${CMAKE_CMAKE_COMMAND}
Add stronger infrastructure for CMake-only tests The CMakeOnly directory added by commit 9a20abf0 (Add infrastructure for CMake-only tests, 2012-01-11) was sufficient only for tests that always run CMake to successfully configure a project. Later commit eeaaffcb (find_package: Test error and warning messages in failure cases, 2012-02-28) added a sample test that covers failure cases. Generalize the above to create new "RunCMake" test infrastructure that can run CMake multiple times for a single project with different variations and check for expected result/stdout/stderr. Allow for both successful and failing CMake project configuration cases. This will be useful to test error messages and failure behavior.
2012-03-10 01:24:43 +04:00
-DCMAKE_MODULE_PATH=${CMAKE_CURRENT_SOURCE_DIR}
Tests: Drop CMAKE_TEST_GENERATOR(|_TOOLSET) variables s/CMAKE_TEST_GENERATOR/CMAKE_GENERATOR/g
2014-03-03 23:06:34 +04:00
-DRunCMake_GENERATOR=${CMAKE_GENERATOR}
Tests: Add generator platform support Propagate CMAKE_GENERATOR_PLATFORM through the test hierarchy so that all tests can build with the selected generator platform, if any.
2014-09-05 23:40:01 +04:00
-DRunCMake_GENERATOR_PLATFORM=${CMAKE_GENERATOR_PLATFORM}
Tests: Drop CMAKE_TEST_GENERATOR(|_TOOLSET) variables s/CMAKE_TEST_GENERATOR/CMAKE_GENERATOR/g
2014-03-03 23:06:34 +04:00
-DRunCMake_GENERATOR_TOOLSET=${CMAKE_GENERATOR_TOOLSET}
Tests/RunCMake: Honor CMAKE_MAKE_PROGRAM If tests are using an explicit make program, pass it through to RunCMake tests so that any that actually do build use the expected tool.
2015-01-24 15:08:12 +03:00
-DRunCMake_MAKE_PROGRAM=${CMake_TEST_EXPLICIT_MAKE_PROGRAM}
RunCMake: Allow specifying the directory to run tests in.
2015-02-09 10:39:18 +03:00
-DRunCMake_SOURCE_DIR=${CMAKE_CURRENT_SOURCE_DIR}/${Test_Dir}
Add stronger infrastructure for CMake-only tests The CMakeOnly directory added by commit 9a20abf0 (Add infrastructure for CMake-only tests, 2012-01-11) was sufficient only for tests that always run CMake to successfully configure a project. Later commit eeaaffcb (find_package: Test error and warning messages in failure cases, 2012-02-28) added a sample test that covers failure cases. Generalize the above to create new "RunCMake" test infrastructure that can run CMake multiple times for a single project with different variations and check for expected result/stdout/stderr. Allow for both successful and failing CMake project configuration cases. This will be useful to test error messages and failure behavior.
2012-03-10 01:24:43 +04:00
-DRunCMake_BINARY_DIR=${CMAKE_CURRENT_BINARY_DIR}/${test}
Xcode: Implement generator toolset selection (#9831, #13802) Implement generator toolset selection (cmake -T) for Xcode > 2.0 by adding the GCC_VERSION build setting to project files.
2012-12-20 19:16:57 +04:00
${${test}_ARGS}
RunCMake: Allow specifying the directory to run tests in.
2015-02-09 10:39:18 +03:00
${TEST_ARGS}
-P "${CMAKE_CURRENT_SOURCE_DIR}/${Test_Dir}/RunCMakeTest.cmake"
Add stronger infrastructure for CMake-only tests The CMakeOnly directory added by commit 9a20abf0 (Add infrastructure for CMake-only tests, 2012-01-11) was sufficient only for tests that always run CMake to successfully configure a project. Later commit eeaaffcb (find_package: Test error and warning messages in failure cases, 2012-02-28) added a sample test that covers failure cases. Generalize the above to create new "RunCMake" test infrastructure that can run CMake multiple times for a single project with different variations and check for expected result/stdout/stderr. Allow for both successful and failing CMake project configuration cases. This will be useful to test error messages and failure behavior.
2012-03-10 01:24:43 +04:00
)
endmacro()
Use generalized RunCMake test infrastrucure for find_package test
2012-03-10 01:34:09 +04:00
Tests: Add RunCMake tests for CPack{Deb,RPM} Add script structure for easier addition of new CPack related tests.
2015-06-05 22:03:26 +03:00
function(add_RunCMake_test_group test types)
# create directory for common content
set(TEST_CONFIG_DIR "${CMAKE_CURRENT_BINARY_DIR}/${test}/conf")
file(REMOVE_RECURSE "${TEST_CONFIG_DIR}")
file(MAKE_DIRECTORY "${TEST_CONFIG_DIR}")
foreach(type IN LISTS types)
# generate prerequirements config file in cmake as ctest doesn't have as
# much system information so it is easier to set programs and environment
# values here
unset(${test}_${type}_FOUND_PREREQUIREMENTS)
include("${CMAKE_CURRENT_SOURCE_DIR}/${test}/${type}/Prerequirements.cmake")
get_test_prerequirements("${test}_${type}_FOUND_PREREQUIREMENTS"
"${TEST_CONFIG_DIR}/${type}_config.cmake")
# only add the test if prerequirements are met
if(${test}_${type}_FOUND_PREREQUIREMENTS)
add_test(NAME RunCMake.${test}_${type} COMMAND ${CMAKE_CMAKE_COMMAND}
-DTEST_TYPE=${type}
-DCMAKE_MODULE_PATH=${CMAKE_CURRENT_SOURCE_DIR}
-DRunCMake_GENERATOR=${CMAKE_GENERATOR}
-DRunCMake_GENERATOR_PLATFORM=${CMAKE_GENERATOR_PLATFORM}
-DRunCMake_GENERATOR_TOOLSET=${CMAKE_GENERATOR_TOOLSET}
-DRunCMake_MAKE_PROGRAM=${CMake_TEST_EXPLICIT_MAKE_PROGRAM}
-DRunCMake_SOURCE_DIR=${CMAKE_CURRENT_SOURCE_DIR}/${test}
-DRunCMake_BINARY_DIR=${CMAKE_CURRENT_BINARY_DIR}/${type}/${test}
-Dconfig_file=${TEST_CONFIG_DIR}/${type}_config.cmake
-P "${CMAKE_CURRENT_SOURCE_DIR}/${test}/RunCMakeTest.cmake"
)
endif()
endforeach()
endfunction()
Add rudimentary support for the Apple Swift language with Xcode Allow the `Swift` language to be enabled with the Xcode generator for Xcode >= 6.1. Reject it on other generators and with older Xcode versions. Since Apple is the only vendor implementing the language right now, the compiler id can be just `Apple`.
2015-07-06 23:15:49 +03:00
if(XCODE_VERSION AND "${XCODE_VERSION}" VERSION_LESS 6.1)
set(Swift_ARGS -DXCODE_BELOW_6_1=1)
endif()
Xcode: Implement generator toolset selection (#9831, #13802) Implement generator toolset selection (cmake -T) for Xcode > 2.0 by adding the GCC_VERSION build setting to project files.
2012-12-20 19:16:57 +04:00
if(XCODE_VERSION AND "${XCODE_VERSION}" VERSION_LESS 3)
set(GeneratorToolset_ARGS -DXCODE_BELOW_3=1)
endif()
Tests: Fix RunCMake.TargetSources on Xcode 1.5 Xcode 1.5 does not support multiple configurations. The generator also adds some sources internally that cause extra OriginDebug output. Update the expected output to tolerate it.
2014-06-06 18:01:07 +04:00
if(XCODE_VERSION AND "${XCODE_VERSION}" VERSION_LESS 2)
set(TargetSources_ARGS -DXCODE_BELOW_2=1)
Tests: Activate tests accidentally excluded from Xcode The generator name is "Xcode", not "XCode". Fix this typo. Explicitly exclude the SubDirSpaces test on Xcode because it does not work. Also tell the RunCMake.File_Generate test when Xcode is not multi-config so it can exlcude the OutputConflict case. Inspired-by: Daniele E. Domenichelli <daniele.domenichelli@iit.it>
2014-07-17 17:31:53 +04:00
set(File_Generate_ARGS -DXCODE_BELOW_2=1)
Tests: Fix RunCMake.TargetSources on Xcode 1.5 Xcode 1.5 does not support multiple configurations. The generator also adds some sources internally that cause extra OriginDebug output. Update the expected output to tolerate it.
2014-06-06 18:01:07 +04:00
endif()
Genex: Implement generator expressions for target PDB files.
2014-07-25 00:18:21 +04:00
# Test MSVC for older host CMake versions, and test
# WIN32/CMAKE_C_COMPILER_ID to fix check on Intel for Windows.
if(MSVC OR (WIN32 AND CMAKE_C_COMPILER_ID MATCHES "MSVC|Intel"))
set(GeneratorExpression_ARGS -DLINKER_SUPPORTS_PDB=1)
endif()
Add policy CMP0019 to skip include/link variable re-expansion Historically CMake has always expanded ${} variable references in the values given to include_directories(), link_directories(), and link_libraries(). This has been unnecessary since general ${} evaluation syntax was added to the language a LONG time ago, but has remained for compatibility with VERY early CMake versions. For a long time the re-expansion was a lightweight operation because it was only processed once at the directory level and the fast-path of cmMakefile::ExpandVariablesInString was usually taken because values did not have any '$' in them. Then commit d899eb71 (Call ExpandVariablesInString for each target's INCLUDE_DIRECTORIES, 2012-02-22) made the operation a bit heavier because the expansion is now needed on a per-target basis. In the future we will support generator expressions in INCLUDE_DIRECTORIES with $<> syntax, so the fast-path in cmMakefile::ExpandVariablesInString will no longer be taken and re-expansion will be very expensive. Add policy CMP0019 to skip the re-expansion altogether in NEW behavior. In OLD behavior perform the expansion but improve the fast-path heuristic to match ${} but not $<>. If the policy is not set then warn if expansion actually does anything. We expect this to be encountered very rarely in practice.
2012-12-06 18:59:18 +04:00
add_RunCMake_test(CMP0019)
Introduce the INTERFACE_LINK_LIBRARIES property. This property replaces the properties which match (IMPORTED_)?LINK_INTERFACE_LIBRARIES(_<CONFIG>)?, and is enabled for IMPORTED targets, and for non-IMPORTED targets only with a policy. For static libraries, the INTERFACE_LINK_LIBRARIES property is also used as the source of transitive usage requirements content. Static libraries still require users to link to all entries in their LINK_LIBRARIES, but usage requirements such as INCLUDE_DIRECTORIES COMPILE_DEFINITIONS and COMPILE_OPTIONS can be restricted to only certain interface libraries. Because the INTERFACE_LINK_LIBRARIES property is populated unconditionally, we need to compare the evaluated result of it with the link implementation to determine whether to issue the policy warning for static libraries. For shared libraries, the policy warning is issued if the contents of the INTERFACE_LINK_LIBRARIES property differs from the contents of the relevant config-specific old LINK_INTERFACE_LIBRARIES property.
2013-06-04 18:25:47 +04:00
add_RunCMake_test(CMP0022)
cmTarget: Deprecate the LOCATION target property with a policy. The final location and name of a build-target is not determined until generate-time. However, reading the LOCATION property from a target is currently allowed at configure time. Apart from creating possibly-erroneous results, this has an impact on the implementation of cmake itself, and prevents some major cleanups from being made. Disallow reading LOCATION from build-targets with a policy. Port some existing uses of it in CMake itself to use the TARGET_FILE generator expression.
2013-06-28 18:37:39 +04:00
add_RunCMake_test(CMP0026)
Handle genexes when evaluating INTERFACE_INCLUDE_DIRECTORIES errors.
2013-06-18 18:33:33 +04:00
add_RunCMake_test(CMP0027)
Consider targets with double colons to be IMPORTED or ALIAS targets. Introduce a policy to control the behavior. The AliasTargets unit test already tests that using a double-semicolon in the name is not an error. Change the ExportImport test to use a namespace with a double-semicolon too.
2013-07-30 11:51:56 +04:00
add_RunCMake_test(CMP0028)
Enable RunCMake.CMP0037 test everywhere Split the test cases covering spaces and colons into separate units. Run the space cases everywhere. Disable the colon cases where they are known to fail. This approach increases platform coverage for the test and makes the known-failure logic as local as possible. No Makefile generator on Windows can generate targets with ':' in their name because the CMakeFiles/<target>.dir directory cannot be created. Skip this part of the test on all Windows Make tools.
2013-11-08 20:44:55 +04:00
add_RunCMake_test(CMP0037)
Disallow link-to-self (#13947).
2013-11-05 21:01:09 +04:00
add_RunCMake_test(CMP0038)
Disallow linking to utility targets (#13902).
2013-11-05 22:15:53 +04:00
add_RunCMake_test(CMP0039)
Add policy CMP0040 to disallow custom commands on missing targets
2013-11-20 12:53:06 +04:00
add_RunCMake_test(CMP0040)
Export: Report error on relative include with genex. Diagnostics which check the sanity of exported include paths previously skipped over any path containing a generator expression. Introduce a policy to issue an error message in such cases. The export files created in the OLD behavior are not usable, because they contain relative paths or paths to the source or build location which are not suitable for use on installation. CMake will report an error on import.
2013-11-26 14:24:47 +04:00
add_RunCMake_test(CMP0041)
OS X: Add CMP0042 to enable MACOSX_RPATH by default Also adding documentation for CMAKE_MACOSX_RPATH, and improving documentation for MACOSX_RPATH.
2013-12-19 08:25:29 +04:00
if(CMAKE_SYSTEM_NAME MATCHES Darwin AND CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG)
add_RunCMake_test(CMP0042)
endif()
cmTarget: Deprecate COMPILE_DEFINITIONS_ properties with a policy.
2013-12-30 16:33:02 +04:00
add_RunCMake_test(CMP0043)
get_target_property: Error on non-existent target. Introduce policy CMP0045 to control this behavior.
2014-01-08 16:16:33 +04:00
add_RunCMake_test(CMP0045)
AddDependencies: new policy requires dependencies to exist Added new policy CMP0046 which requires dependencies added by add_dependencies() to actually exist.
2014-01-12 15:58:04 +04:00
add_RunCMake_test(CMP0046)
Add policy CMP0049 to avoid variable expansion in source lists
2014-02-11 20:41:24 +04:00
add_RunCMake_test(CMP0049)
add_custom_command: Disallow use of SOURCE signatures. Add CMP0050 to control this behavior.
2014-02-11 21:39:55 +04:00
add_RunCMake_test(CMP0050)
cmTarget: Include TARGET_OBJECTS genex in target SOURCES property. Add policy CMP0051 to control this behavior.
2014-03-18 19:15:15 +04:00
add_RunCMake_test(CMP0051)
tests: test CMP0053 in WARN mode when watching variables When CMP0053 is in WARN mode, variables get expanded twice, leaking the fact that the string was expanded twice and changing behavior. Instead, suppress variable watches when running the expansion to trigger the CMP0053 warning.
2014-05-21 01:00:28 +04:00
add_RunCMake_test(CMP0053)
If: Introduce policy CMP0054 - don't dereference quoted variables in if()
2014-09-04 22:21:28 +04:00
add_RunCMake_test(CMP0054)
break: Add policy CMP0055 to check calls strictly Reject break() without loop scope or any arguments. Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
2014-11-18 18:34:32 +03:00
add_RunCMake_test(CMP0055)
if: Implement new IN_LIST operator
2015-04-29 18:25:13 +03:00
add_RunCMake_test(CMP0057)
Do not treat DEFINITIONS as a built-in directory property Add policy CMP0059 to cover this change. The property has been deprecated since CMake 2.4 anyway. This will help clean up cmMakefile -- the DefineFlagsOrig member should not need to exist.
2015-04-01 21:53:31 +03:00
add_RunCMake_test(CMP0059)
Link libraries by full path even in implicit directories When CMP0003 was first introduced we wanted to link all libraries by full path. However, some projects had problems on platforms where find_library would find /usr/lib/libfoo.so when the project really wanted to link to /usr/lib/<arch>/libfoo.so and had been working by accident because pre-CMP0003 behavior used -lfoo to link. We first tried to address that in commit v2.6.0~440 (Teach find_library to avoid returning library paths in system directories, 2008-01-23) by returning just "foo" for libraries in implicit link directories. This caused problems for projects expecting find_library to always return a full path. We ended up using the solution in commit v2.6.0~366 (... switch library paths found in implicit link directories to use -l, 2008-01-31). However, the special case for libraries in implicit link directories has also proven problematic and confusing. Introduce policy CMP0060 to switch to linking all libraries by full path even if they are in implicit link directories. Explain in the policy documentation the factors that led to the original approach and now to this approach.
2015-04-07 17:43:47 +03:00
add_RunCMake_test(CMP0060)
if: Add "TEST <test>" condition if(TEST TestNameThatExists) will return true if a test with the name TestNameThatExists has been added with add_test. The syntax is similar to if(TARGET TargetName). Since use of "TEST" as an argument to if() could previously be interpreted as a non-keyword argument, add policy CMP0064 to treat it as a keyword as NEW behavior.
2014-12-30 04:47:48 +03:00
add_RunCMake_test(CMP0064)
Tests: Add test for TARGET_MESSAGES global property
2015-07-14 20:31:21 +03:00
if(CMAKE_GENERATOR MATCHES "Make")
add_RunCMake_test(Make)
endif()
Ninja: Add policy to require explicit custom command byproducts Add policy CMP0058 to avoid generating 'phony' ninja rules for unknown custom command dependencies. This requires projects to specify their custom command byproducts explicitly. With this requirement we no longer have to assume that unknown custom command dependencies are generated and can instead simply assume they are source files expected to exist when the build starts. This is particularly important in in-source builds. It is also helpful for out-of-source builds to allow Ninja to diagnose missing files before running custom command rules that depend on them.
2015-03-20 23:43:21 +03:00
if(CMAKE_GENERATOR STREQUAL "Ninja")
add_RunCMake_test(Ninja)
endif()
CTest: Fail early without PROJECT_BINARY_DIR (#14005) Do not use PROJECT_BINARY_DIR before it is defined. If it is not defined when needed, fail with an error message suggesting that the project() command be invoked first.
2013-03-13 02:20:01 +04:00
add_RunCMake_test(CTest)
Tests: Move CTestTestMemcheck cases into a RunCMake.CTestMemcheck test The CTestTestMemcheck test cases all try to check the ctest output with a regular expression. They fail intermittently due to ordering of the portions of the output that come from stdout and stderr being mixed. Convert all the test cases to use the RunCMake infrastructure to match stdout and stderr separately.
2014-12-16 21:50:30 +03:00
if(NOT CMake_TEST_EXTERNAL_CMAKE)
Tests: Rename RunCMake.{CTestMemcheck => ctest_memcheck} Follow the convention of naming tests after the command they test.
2015-02-19 19:35:51 +03:00
add_RunCMake_test(ctest_memcheck
Tests: Move CTestTestMemcheck cases into a RunCMake.CTestMemcheck test The CTestTestMemcheck test cases all try to check the ctest output with a regular expression. They fail intermittently due to ordering of the portions of the output that come from stdout and stderr being mixed. Convert all the test cases to use the RunCMake infrastructure to match stdout and stderr separately.
2014-12-16 21:50:30 +03:00
-DPSEUDO_BC=$<TARGET_FILE:pseudo_BC>
-DPSEUDO_PURIFY=$<TARGET_FILE:pseudo_purify>
-DPSEUDO_VALGRIND=$<TARGET_FILE:pseudo_valgrind>
-DPSEUDO_BC_NOLOG=$<TARGET_FILE:pseudonl_BC>
-DPSEUDO_PURIFY_NOLOG=$<TARGET_FILE:pseudonl_purify>
-DPSEUDO_VALGRIND_NOLOG=$<TARGET_FILE:pseudonl_valgrind>
-DMEMCHECK_FAIL=$<TARGET_FILE:memcheck_fail>
)
endif()
Tests: Add RunCMake.BuildDepends test This will allow more granular checks than the main BuildDepends test. Start with a simple single-source C program.
2015-09-16 17:09:07 +03:00
add_RunCMake_test(BuildDepends)
Ninja: Prevent compilers to be silently modified Unlike with Unix Makefiles generator modifying compiler paths was not protected with Ninja generator. It was possible to modify them in the cache without the expected effect on the generated solution. Also activate corresponding tests with Ninja.
2014-09-21 00:37:52 +04:00
if(UNIX AND "${CMAKE_GENERATOR}" MATCHES "Unix Makefiles|Ninja")
Test Unix Makefiles generator support for changing compilers Add RunCMake.CompilerChange test to cover use of -DCMAKE_C_COMPILER=cc to change the compiler of an existing build tree. Also test for proper failure with -DCMAKE_C_COMPILER="" and no CC in the environment.
2013-02-18 19:35:53 +04:00
add_RunCMake_test(CompilerChange)
endif()
Require CMAKE_<LANG>_COMPILER to be found as a full path All generators now support detection of the full path to the compiler, so require it to be so. This will allow CMake<LANG>Information.cmake and other logic to assume the full path to the compiler tool is available. The Makefile generators already rejected CMAKE_<LANG>_COMPILER values that did not name an existing compiler. Extend this error message to all generators, make it occur as early as possible, and improve the message with advice about how to set the compiler. If the full path to the compiler is not known, finish enabling languages with a fatal error so configuration does not continue. For now, allow the RC language compiler to not be a full path. Later we will need to detect the full path to "rc" under the VS IDE. Add a RunCMake.CompilerNotFound test to cover failure cases. Fix the RunCMake.CompilerChange test EmptyCompiler case to work when configuration does not continue past enable_language.
2013-10-24 21:04:24 +04:00
add_RunCMake_test(CompilerNotFound)
cmake: On configure error suggest looking at CMake*.log files When CMake reports failure to configure a project, especially when the toolchain does not initialize properly, the true reason may be clear from reading the CMakeFiles/CMake(Output|Error).log files. Advise users to look at these files if they exist when configuration fails. Add RunCMake.Configure test to check that the log files are mentioned when configuration fails.
2013-07-09 22:35:49 +04:00
add_RunCMake_test(Configure)
Add infrastructure for policies that disallow commands Add cmCommand::Disallowed helper to check the setting of a policy that disallows the command. Add a RunCMake.DisallowedCommands test placeholder. Add a Help/policy/DISALLOWED_COMMAND.txt file for inclusion by each policy document to avoid duplication of the common text.
2013-10-18 19:54:09 +04:00
add_RunCMake_test(DisallowedCommands)
ExternalData: Add tests covering interfaces and errors Add a Module.ExternalData test to verify data retrieval and test argument DATA{} references. Add a RunCMake.ExternalData test to verify error handling and automatic transformation of a raw data to a content link and staged object.
2013-01-26 01:39:57 +04:00
add_RunCMake_test(ExternalData)
FeatureSummary: Add unit tests
2014-03-03 22:51:57 +04:00
add_RunCMake_test(FeatureSummary)
FPHSA: Convert FOUND_VAR failure test to RunCMake Move the Tests/FPHSA_InvalidFOUND_VAR test case over to a new RunCMake.FPHSA test with a BadFoundVar case. The RunCMake tests are built to cover failure cases easily and robustly.
2013-02-22 17:44:13 +04:00
add_RunCMake_test(FPHSA)
Add boolean generator expressions Add generator expressions that combine and use boolean test results: $<0:...> = empty string (ignores "...") $<1:...> = content of "..." $<AND:?[,?]...> = '1' if all '?' are '1', else '0' $<OR:?[,?]...> = '0' if all '?' are '0', else '1' $<NOT:?> = '0' if '?' is '1', else '1' These will be useful to evaluate (future) boolean query expressions and condition content on the results. Include tests and documentation.
2012-08-13 17:49:53 +04:00
add_RunCMake_test(GeneratorExpression)
CMake: Add CMAKE_GENERATOR_PLATFORM option Reject the option by default. It will be implemented on a per-generator basis. Pass the setting into try_compile project generation. Add cache entry CMAKE_GENERATOR_PLATFORM and associated variable documentation to hold the value persistently. Add a RunCMake.GeneratorPlatform test to cover basic use cases for the option. Verify that CMAKE_GENERATOR_PLATFORM is empty by default, and that it is rejected when the generator does not support a user setting.
2014-09-05 22:25:27 +04:00
add_RunCMake_test(GeneratorPlatform)
CMake: Add -T option to choose a generator toolset Reject the option by default. It will be implemented on a per-generator basis. Pass the setting into try_compile project generation. Add cache entry CMAKE_GENERATOR_TOOLSET and associated variable documentation to hold the value persistently. Add a RunCMake.GeneratorToolset test to cover basic "-T" option cases. Verify that CMAKE_GENERATOR_TOOLSET is empty without -T, that -T is rejected when the generator doesn't support it, and that two -T options are always rejected.
2012-12-10 19:42:33 +04:00
add_RunCMake_test(GeneratorToolset)
GNUInstallDirs: Add test cases Add a RunCMake.GNUInstallDirs test with cases covering various install prefixes. Hard-code the architecture information. Tolerate all platform-specific LIBDIR values. Currently the root prefix is not handled well, but verify the current behavior in the test anyway. This can be addressed with a future change. Inspired-by: Alex Turbov <i.zaufi@gmail.com>
2015-06-16 21:59:51 +03:00
add_RunCMake_test(GNUInstallDirs)
Process generator expressions in the INCLUDE_DIRECTORIES property. This use of generator expressions, like all others to come which operate on target properties, must initalize the dag checker.
2012-09-18 15:57:07 +04:00
add_RunCMake_test(TargetPropertyGeneratorExpressions)
Do not crash on SHARED library without language (#13324) Since commit e1409ac5 (Support building shared libraries or modules without soname, 2012-04-22) CMake crashes on the code add_library(foo SHARED foo.nolang) because the logic to lookup the language's soname flag was moved from cmTarget::GetLibraryNames to cmMakefile::GetSONameFlag without its check for a NULL language. Restore the check for NULL. Add RunCMake.Languages test to cover language error cases like this one.
2012-06-20 19:04:35 +04:00
add_RunCMake_test(Languages)
Tests: Move LINK_SEARCH_{START,END}_STATIC case to dedicated test The test case added to RunCMake.set_property by commit 675ef165 (Allow LINK_SEARCH_{START,END}_STATIC props to have default values, 2015-08-07) is not a test of the set_property command and so belongs in its own test case. Create a new RunCMake.LinkStatic test to cover cases related to static linking. While at it, simplify the LINK_SEARCH_STATIC test case to enable only C.
2015-09-02 23:09:22 +03:00
add_RunCMake_test(LinkStatic)
Test OBJECT library failure cases Add "RunCMake.ObjectLibrary" test to verify that unsupported use cases are rejected with errors: * An OBJECT library may not reference another object library * An OBJECT library may not be referenced in target_link_libraries * An OBJECT library may not contain non-compiling sources * An OBJECT library may not have pre/post build/link commands * An OBJECT library may not be installed, exported, or imported Also verify that invalid $<TARGET_OBJECTS:...> expressions are diagnosed.
2012-03-12 22:51:30 +04:00
add_RunCMake_test(ObjectLibrary)
Add rudimentary support for the Apple Swift language with Xcode Allow the `Swift` language to be enabled with the Xcode generator for Xcode >= 6.1. Reject it on other generators and with older Xcode versions. Since Apple is the only vendor implementing the language right now, the compiler id can be just `Apple`.
2015-07-06 23:15:49 +03:00
add_RunCMake_test(Swift)
Genex: Evaluate TARGET_OBJECTS as a normal expression.
2014-02-26 18:59:18 +04:00
add_RunCMake_test(TargetObjects)
cmTarget: Make the source files depend on the config. Disallow the use of config-specific source files with the Visual Studio and Xcode generators. They don't have any way to represent the condition currently. Use the same common-config API in cmQtAutoGenerators. While it accepts config-specific files, it doesn't have to support multiple configurations yet. Loop over the configs in cmTargetTraceDependencies and cmGlobalGenerator::WriteSummary and consume all source files. Loop over the configs in cmComputeTargetDepends and compute the object library dependencies for each config.
2014-02-13 20:25:00 +04:00
add_RunCMake_test(TargetSources)
Test error cases in find_dependency.
2014-03-11 17:36:58 +04:00
add_RunCMake_test(find_dependency)
CompileDefinitions: Add unit test for setting empty content.
2015-07-21 23:52:44 +03:00
add_RunCMake_test(CompileDefinitions)
Features: Add cxx_auto_type. Record the availability of this feature for GNU 4.8 on (UNIX AND NOT APPLE) only. In the future, availability can be recorded for earlier GNU, for other platforms and for other compilers. Initially the affected configurations are as restricted as possible to allow for easy testing while extending the features vector in only one dimension. The error message when using the set_property API directly is not very good, but follow up commits will provide origin debugging of the property and a target_compile_features command which will provide a configure-time backtrace when possible.
2014-04-02 17:34:16 +04:00
add_RunCMake_test(CompileFeatures)
Tests: Verify generate-time policy scope behavior. If some day there are no policies checked through the makefile at generate time, this can be fixed.
2015-08-01 08:16:40 +03:00
add_RunCMake_test(PolicyScope)
Add the WriteCompilerDetectionHeader module. Provide a function to write a portable header to detect compiler features. Generate a preprocessor #error for unknown compilers and compiler versions whose features are not yet recorded. This error condition might be relaxed in the future, but for now it is useful for verification of expectations.
2013-10-21 18:59:40 +04:00
add_RunCMake_test(WriteCompilerDetectionHeader)
Process the INTERFACE_PIC property from linked dependencies This allows a dependee to inform a target that it should have its POSITION_INDEPENDENT_CODE property set to ON, or OFF. The value of the POSITION_INDEPENDENT_CODE property, if set, must be consistent with any INTERFACE_POSITION_INDEPENDENT_CODE properties on dependees. Add a test covering the consistency checks on platforms where they run.
2012-11-05 15:46:26 +04:00
if(NOT WIN32)
add_RunCMake_test(PositionIndependentCode)
Tests: Refactor RunCMake.VisibilityPreset test setup Enable languages only in the individual test case. Enable the test everywhere except Visual Studio generators (which do not implement the properties) and just set fake flags as needed to activate relevant code paths. Drop unneeded CMAKE_SUPPRESS_REGENERATION which seems to have been copied from an unrelated test when this test was created.
2015-05-22 17:43:34 +03:00
endif()
if(NOT CMAKE_GENERATOR MATCHES "Visual Studio")
add_RunCMake_test(VisibilityPreset)
Process the INTERFACE_PIC property from linked dependencies This allows a dependee to inform a target that it should have its POSITION_INDEPENDENT_CODE property set to ON, or OFF. The value of the POSITION_INDEPENDENT_CODE property, if set, must be consistent with any INTERFACE_POSITION_INDEPENDENT_CODE properties on dependees. Add a test covering the consistency checks on platforms where they run.
2012-11-05 15:46:26 +04:00
endif()
cmTarget: Require a compatible INTERFACE_AUTOUIC_OPTIONS from dependencies. Revert the origin-tracking infrastructure from commit 98093c45 (QtAutoUic: Add INTERFACE_AUTOUIC_OPTIONS target property., 2013-11-20). Use the compatibility-tracking for compatible strings instead. If two different dependencies require different AUTOUIC_OPTIONS, cmake will now appropriately issue an error.
2013-12-03 16:26:51 +04:00
if (QT4_FOUND)
set(CompatibleInterface_ARGS -DQT_QMAKE_EXECUTABLE:FILEPATH=${QT_QMAKE_EXECUTABLE})
endif()
Make INTERFACE determined properties readable in generator expressions. The properties are evaluated as link-dependent interface properties when evaluating the generator expressions.
2013-01-19 14:21:14 +04:00
add_RunCMake_test(CompatibleInterface)
Add RunCMake.Syntax test to cover argument parsing Test basic unquoted and quoted argument parsing cases including failure on an unterminated string and an unterminated command invocation. Also cover arguments not separated by any spaces, which is accidentally allowed by the current parser.
2012-08-06 17:29:20 +04:00
add_RunCMake_test(Syntax)
Test OBJECT library failure cases Add "RunCMake.ObjectLibrary" test to verify that unsupported use cases are rejected with errors: * An OBJECT library may not reference another object library * An OBJECT library may not be referenced in target_link_libraries * An OBJECT library may not contain non-compiling sources * An OBJECT library may not have pre/post build/link commands * An OBJECT library may not be installed, exported, or imported Also verify that invalid $<TARGET_OBJECTS:...> expressions are diagnosed.
2012-03-12 22:51:30 +04:00
Tests: Test add_custom_command and add_custom_target error cases Add RunCMake.add_custom_command and RunCMake.add_custom_target tests to cover the error messages for these commands.
2014-11-13 20:46:49 +03:00
add_RunCMake_test(add_custom_command)
add_RunCMake_test(add_custom_target)
add_dependencies: Distinguish target v. file dependencies in error (#14050) When called with a non-existent LHS target name the user may be trying to add file-level dependencies. Clarify the error message to explain the difference between target-level and file-level dependencies. Point the reader at the commands and options needed for the latter.
2013-03-29 22:53:36 +04:00
add_RunCMake_test(add_dependencies)
add_subdirectory: Fix error message on missing CMakeLists.txt (#15680) Refactoring in commit v3.3.0-rc1~76^2 (cmMakefile: Handle CMP0014 before configuring the generator, 2015-05-14) accidentally left the file name "/CMakeLists.txt" in the error message. Remove it and add a test case.
2015-08-04 23:39:31 +03:00
add_RunCMake_test(add_subdirectory)
Use generalized RunCMake test infrastrucure for build_command test The CMakeCommands.build_command test performs output/error checking so move it over to RunCMake to re-use the generalized infrastrucure. This is the only test left using Tests/CMakeCommands/CMakeLists.txt so remove it.
2012-03-10 01:47:19 +04:00
add_RunCMake_test(build_command)
execute_process: Improve stdout/stderr merging Use the KWSys Process "MergeOutput" option to give the child process the same pipe (or file) for both stdout and stderr. This allows natural merging of stdout and stderr together instead of merging on arbitrary buffered read boundaries as before.
2015-05-07 21:40:38 +03:00
add_RunCMake_test(execute_process)
export(): Check targets exist at configure-time (#14608) Commit 66b290e7 (export(): Process the export() command at generate time., 2012-10-06 ) refactored export() so that it could evaluate strings at generate-time. This was intended for evaluating target properties, but that commit also removed a check for target existence at configure-time. Restore that check and add a test for this case.
2013-12-02 20:18:29 +04:00
add_RunCMake_test(export)
Drop compatibility with CMake < 2.4 Drop all behavior activated by setting CMAKE_BACKWARDS_COMPATIBILITY to a value lower than 2.4, and generate an error when projects or the user attempt to do so. In the error suggest using a CMake 2.8.x release. Teach cmake_minimum_required to warn about projects that do not require at least CMake 2.4. They are not supported by CMake >= 3.0. Replace the documentation of CMAKE_BACKWARDS_COMPATIBILITY with a reference to policy CMP0001.
2013-10-18 19:25:49 +04:00
add_RunCMake_test(cmake_minimum_required)
continue: Add a new CMake language command for loop continuation (#14013) Inspired-by: Doug Barbieri Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
2014-11-29 19:56:18 +03:00
add_RunCMake_test(continue)
ctest_build: Add QUIET option
2015-02-17 21:41:40 +03:00
add_RunCMake_test(ctest_build)
ctest_configure: Add QUIET option
2015-02-17 20:38:52 +03:00
add_RunCMake_test(ctest_configure)
ctest_coverage: Add QUIET option
2015-02-17 23:57:26 +03:00
if(COVERAGE_COMMAND)
add_RunCMake_test(ctest_coverage -DCOVERAGE_COMMAND=${COVERAGE_COMMAND})
endif()
ctest_start: Add QUIET option This suppresses all non-error messages that would have otherwise been printed by this function.
2015-02-17 17:58:25 +03:00
add_RunCMake_test(ctest_start)
Tests: Rename RunCMake.{CTestSubmit => ctest_submit} Follow the convention of naming tests after the command they test.
2015-02-19 19:33:32 +03:00
add_RunCMake_test(ctest_submit)
ctest_test: Add QUIET option
2015-02-17 22:23:56 +03:00
add_RunCMake_test(ctest_test)
ctest_upload: Add QUIET option
2015-02-18 17:15:29 +03:00
add_RunCMake_test(ctest_upload)
file: Report system error on failure to open file
2014-05-20 18:42:13 +04:00
add_RunCMake_test(file)
Teach find_(library|file|path) to get prefixes from PATH (#15370) The find_package command already knows how to compute installation prefixes from PATH. Use the same approach to establish prefixes for find_library, find_file, and find_path to use to look in directories like "<prefix>/lib[/<arch>]" and "<prefix>/include" for libraries and headers. This will reduce the amount of configuration end users need to do to establish a work environment rooted under a specific prefix.
2015-02-18 18:54:45 +03:00
add_RunCMake_test(find_file)
find_library: Fix repeat call after changing directory content (#15293) We use cmGlobalGenerator::GetDirectoryContent to avoid repeating directory listings. However, GetDirectoryContent loads content from disk at most once. This breaks find_library calls that occur when disk content has changed since preceding find_library calls. Teach cmGlobalGenerator::GetDirectoryContent to save the directory modification time when content is loaded and re-load content if it changes. Create a RunCMake.find_library test with a case covering this.
2014-12-08 23:12:51 +03:00
add_RunCMake_test(find_library)
Use generalized RunCMake test infrastrucure for find_package test
2012-03-10 01:34:09 +04:00
add_RunCMake_test(find_package)
Teach find_(library|file|path) to get prefixes from PATH (#15370) The find_package command already knows how to compute installation prefixes from PATH. Use the same approach to establish prefixes for find_library, find_file, and find_path to use to look in directories like "<prefix>/lib[/<arch>]" and "<prefix>/include" for libraries and headers. This will reduce the amount of configuration end users need to do to establish a work environment rooted under a specific prefix.
2015-02-18 18:54:45 +03:00
add_RunCMake_test(find_path)
Tests: Add explicit testing for find_program Previously this command was tested only implicitly as part of larger tests. Add a RunCMake.find_program test to cover find_program cases specifically and independently.
2015-09-01 23:33:24 +03:00
add_RunCMake_test(find_program -DCMAKE_SYSTEM_NAME=${CMAKE_SYSTEM_NAME})
get_filename_component: Add explicit unit tests Add test RunCMake.get_filename_component to cover cases of the command. Remove redundant coverage of these cases from the "complex" tests.
2013-04-16 17:27:51 +04:00
add_RunCMake_test(get_filename_component)
tests: add tests for querying properties
2015-01-08 23:27:46 +03:00
add_RunCMake_test(get_property)
if: Add test for IS_DIRECTORY Add a RunCMake.if test to cover if() command behavior. Start with a test for IS_DIRECTORY cases with an existing directory and a long path, both with a trailing slash.
2013-05-28 19:13:24 +04:00
add_RunCMake_test(if)
include: Ignore empty string as file name (#13388) Previously CMake silently accepted the empty string and added a bogus dependency on the current directory. Instead warn about the empty file name and ignore it. We cannot make this an error because there may be existing projects that accidentally depend on the old behavior. Add a RunCMake.include test to cover this case.
2012-07-10 18:55:02 +04:00
add_RunCMake_test(include)
GenEx: Fix reporting about not-found include directories and libraries. This fixes a regression introduced in commit 290e92ad (Move GetIncludeDirectories to cmGeneratorTarget, 2012-09-16) which loops over cmGeneratorTargets before they get created, so the container is empty.
2012-10-15 12:27:42 +04:00
add_RunCMake_test(include_directories)
list: Handle errors on empty lists more gracefully (#13138) Since commit ed1ea24c (Fix INSERT to allow inserting to empty list, 2006-05-15) the list command allows insertion into an empty list at index 0. Fix rejection of insertion at non-zero (negative) indices to present an error message instead of crashing. While at it, fix the error message of the GET and REMOVE_AT operations when the list is empty to not present a bogus allowed range. Add a "RunCMake.list" test to cover failure cases on empty lists.
2012-04-17 18:32:46 +04:00
add_RunCMake_test(list)
message: Add a DEPRECATION mode By default, the message is not issued. If CMAKE_ERROR_DEPRECATED is on, the message is fatal. If CMAKE_WARN_DEPRECATED is on, the message is a warning.
2013-09-17 20:54:34 +04:00
add_RunCMake_test(message)
project: Add optional LANGUAGES keyword Teach the project() command to recognize an optional "LANGUAGES" keyword after the project name and prior to the list of languages. Do not allow multiple copies of the keyword. If the keyword is specified and no languages are listed, imply NONE.
2014-01-29 18:28:01 +04:00
add_RunCMake_test(project)
return: Add test for returning inside a foreach loop Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
2014-11-18 18:34:29 +03:00
add_RunCMake_test(return)
set_property: Fix crash when setting LINK_LIBRARIES to nothing We use a special dedicated structure to store the LINK_LIBRARIES target property. Do not try to construct a string from a NULL value. Instead leave the property structure empty when no value is given. Reported-by: Ghyslain Leclerc <ghleclerc@gmail.com>
2015-07-08 20:14:37 +03:00
add_RunCMake_test(set_property)
string: Add CONCAT sub-command Add a string(CONCAT) command to simply concatenate input arguments together. This will be useful for combining strings from different quoting syntaxes. Add a RunCMake.string test covering these cases.
2013-10-21 20:49:15 +04:00
add_RunCMake_test(string)
try_compile: Add test for bad call error cases Add a RunCMake.try_compile test to cover cases of bad invocation of the try_compile command.
2013-05-15 23:19:20 +04:00
add_RunCMake_test(try_compile)
try_run: Add test for bad link libraries. Based off the corresponding try_compile test.
2015-01-23 03:13:56 +03:00
add_RunCMake_test(try_run)
set: Add unit tests for set/unset PARENT_SCOPE Create a RunCMake.set test to cover set() command cases, starting with PARENT_SCOPE.
2013-11-13 12:18:18 +04:00
add_RunCMake_test(set)
variable_watch: Add test for MODIFIED_ACCESS report Add a RunCMake.variable_watch watch test to cover the basic use case.
2013-06-03 17:23:25 +04:00
add_RunCMake_test(variable_watch)
Tests: Move command failure cases into RunCMake infrastructure Move failure cases from the CMake.{If,List,While,GetProperty} tests over to the RunCMake.{if,list,while,get_property} tests to use the more modern infrastructure. This also avoids using REGEX_ESCAPE_STRING to try to regex-match full paths.
2015-07-14 16:41:05 +03:00
add_RunCMake_test(while)
Add the $<TARGET_POLICY> expression This new expression allows checking how a policy was set when a target was created. That information is only recorded for a subset of policies, so a whitelist is used.
2013-01-16 19:42:39 +04:00
add_RunCMake_test(CMP0004)
Genex: Make CMP0021 and CMP0022 usable with TARGET_POLICY Use preprocessor loops and add a unit test for the appropriate policies. All policies whose value is recorded at target creation time should be part of this list.
2013-06-28 13:25:40 +04:00
add_RunCMake_test(TargetPolicies)
Add the ALIAS target concept for libraries and executables. * The ALIAS name must match a validity regex. * Executables and libraries may be aliased. * An ALIAS acts immutable. It can not be used as the lhs of target_link_libraries or other commands. * An ALIAS can be used with add_custom_command, add_custom_target, and add_test in the same way regular targets can. * The target of an ALIAS can be retrieved with the ALIASED_TARGET target property. * An ALIAS does not appear in the generated buildsystem. It is kept separate from cmMakefile::Targets for that reason. * A target may have multiple aliases. * An ALIAS target may not itself have an alias. * An IMPORTED target may not have an alias. * An ALIAS may not be exported or imported.
2013-07-12 11:14:31 +04:00
add_RunCMake_test(alias_targets)
Add the INTERFACE_LIBRARY target type. This target type only contains INTERFACE_* properties, so it can be used as a structural node. The target-specific commands enforce that they may only be used with the INTERFACE keyword when used with INTERFACE_LIBRARY targets. The old-style target properties matching LINK_INTERFACE_LIBRARIES_<CONFIG> are always ignored for this target type. The name of the INTERFACE_LIBRARY must match a validity generator expression. The validity is similar to that of an ALIAS target, but with the additional restriction that it may not contain double colons. Double colons will carry the meaning of IMPORTED or ALIAS targets in CMake 2.8.13. An ALIAS target may be created for an INTERFACE library. At this point it can not be exported and does not appear in the buildsystem and project files are not created for them. That may be added as a feature in a later commit. The generators need some changes to handle the INTERFACE_LIBRARY targets returned by cmComputeLinkInterface::GetItems. The Ninja generator does not use that API, so it doesn't require changes related to that.
2012-11-02 18:47:40 +04:00
add_RunCMake_test(interface_library)
Allow disabling adding the install prefix to the prefix search path. In certain scenarios, it is preferable to keep a 'dirty' install prefix than to clear it, and to expect that content will not be found there. Add a CMAKE_FIND_NO_INSTALL_PREFIX variable that can be set to disable searching the install prefix.
2013-10-29 13:40:09 +04:00
add_RunCMake_test(no_install_prefix)
Unicode: check encoding of files given to configure_file. UTF-16 and UTF-32 files are rejected.
2014-03-07 09:55:07 +04:00
add_RunCMake_test(configure_file)
include_external_msproject: Test TYPE, GUID, PLATFORM options (#13120) Add "RunCMake.include_external_msproject" test to use the TYPE, GUID, and PLATFORM options to include_external_msproject. Since projects with custom types and platforms cannot be loaded without special VS plugins validate the results by directly parsing the generated solution (.sln). Co-Author: Leonid Yurchenko <nocturne@qarea.com>
2012-04-19 16:35:10 +04:00
FindQt4: Set the INTERFACE_QT_MAJOR_VERSION for Qt4::QtCore With a similar commit in Qt 5, this will error at CMake time if an attempt is made to use target_link_libraries(foo Qt4::QtCore Qt5::Core)
2013-03-16 21:25:59 +04:00
find_package(Qt4 QUIET)
find_package(Qt5Core QUIET)
Fix the Qt 5 version required to run the IncompatibleQt test. The commit to add the INTERFACE_QT_MAJOR_VERSION in qtbase.git is 14054d45 (Set the INTERFACE_QT_MAJOR_VERSION to 5., 2013-03-16) which will be part of Qt 5.1.0. If there is a Qt 5.0.3 release, there is no guarantee it will contain that commit. Make sure such a Qt version does not fail with this test if not.
2013-03-27 03:15:08 +04:00
if (QT4_FOUND AND Qt5Core_FOUND AND NOT Qt5Core_VERSION VERSION_LESS 5.1.0)
FindQt4: Set the INTERFACE_QT_MAJOR_VERSION for Qt4::QtCore With a similar commit in Qt 5, this will error at CMake time if an attempt is made to use target_link_libraries(foo Qt4::QtCore Qt5::Core)
2013-03-16 21:25:59 +04:00
add_RunCMake_test(IncompatibleQt)
endif()
Mark qt4_use_modules and qt4_automoc as obsolete. The QT_QMAKE_EXECUTABLE has to be passed through the cmake calls because the executable may not be in the PATH.
2013-07-04 12:00:27 +04:00
if (QT4_FOUND)
Tests: Simplify RunCMake test extra argument passing Allow add_RunCMake_test calls to pass non-optional arguments immediately.
2014-12-16 00:46:05 +03:00
add_RunCMake_test(ObsoleteQtMacros -DQT_QMAKE_EXECUTABLE:FILEPATH=${QT_QMAKE_EXECUTABLE})
Mark qt4_use_modules and qt4_automoc as obsolete. The QT_QMAKE_EXECUTABLE has to be passed through the cmake calls because the executable may not be in the PATH.
2013-07-04 12:00:27 +04:00
endif()
FindQt4: Set the INTERFACE_QT_MAJOR_VERSION for Qt4::QtCore With a similar commit in Qt 5, this will error at CMake time if an attempt is made to use target_link_libraries(foo Qt4::QtCore Qt5::Core)
2013-03-16 21:25:59 +04:00
FindPkgConfig: Extend PKG_CONFIG_PATH using CMake variables (#12926) Use CMAKE_PREFIX_PATH, CMAKE_FRAMEWORK_PATH, and CMAKE_APPBUNDLE_PATH cache and environment variables to extend PKG_CONFIG_PATH before calling pkg-config. In each of the path in these variables it searches for lib/pkgconfig. Then, depending on the system, it searches for lib/${CMAKE_LIBRARY_ARCHITECTURE}/pkgconfig (debian) or for lib64/pkgconfig (other 64 bit unixes). If any of these path is found, it is appended to the PKG_CONFIG_PATH enviromnent variable. Add two new arguments to the pkg_check_module and pkg_search_module macro, NO_CMAKE_PATH and NO_CMAKE_ENVIRONMENT_PATH. The new signature are therefore: pkg_check_modules(<PREFIX> [REQUIRED] [QUIET] [NO_CMAKE_PATH] [NO_CMAKE_ENVIRONMENT_PATH] <MODULE> [<MODULE>]*) pkg_search_module(<PREFIX> [REQUIRED] [QUIET] [NO_CMAKE_PATH] [NO_CMAKE_ENVIRONMENT_PATH] <MODULE> [<MODULE>]*) By default, if CMAKE_MINIMUM_REQUIRED_VERSION is 3.1 or later (in order to keep compatibility with the previous behavior), or if PKG_CONFIG_USE_CMAKE_PREFIX_PATH is set, the CMAKE_PREFIX_PATH, CMAKE_FRAMEWORK_PATH, and CMAKE_APPBUNDLE_PATH cache and environment variables will be added to pkgconfig search path. The NO_CMAKE_PATH and NO_CMAKE_ENVIRONMENT_PATH arguments disable this behavior for the cache variables and the environment variables, respectively, similarly to the find_package() command.
2014-03-06 21:55:04 +04:00
find_package(PkgConfig QUIET)
if(PKG_CONFIG_FOUND)
add_RunCMake_test(FindPkgConfig)
endif()
Tests: Drop CMAKE_TEST_GENERATOR(|_TOOLSET) variables s/CMAKE_TEST_GENERATOR/CMAKE_GENERATOR/g
2014-03-03 23:06:34 +04:00
if("${CMAKE_GENERATOR}" MATCHES "Visual Studio [^6]")
include_external_msproject: Test TYPE, GUID, PLATFORM options (#13120) Add "RunCMake.include_external_msproject" test to use the TYPE, GUID, and PLATFORM options to include_external_msproject. Since projects with custom types and platforms cannot be loaded without special VS plugins validate the results by directly parsing the generated solution (.sln). Co-Author: Leonid Yurchenko <nocturne@qarea.com>
2012-04-19 16:35:10 +04:00
add_RunCMake_test(include_external_msproject)
Add tests for VS_SOLUTION_GLOBAL_SECTIONS Add tests for correct appliation of directory properties VS_SOLUTION_GLOBAL_SECTIONS_*
2012-10-14 15:15:33 +04:00
add_RunCMake_test(SolutionGlobalSections)
include_external_msproject: Test TYPE, GUID, PLATFORM options (#13120) Add "RunCMake.include_external_msproject" test to use the TYPE, GUID, and PLATFORM options to include_external_msproject. Since projects with custom types and platforms cannot be loaded without special VS plugins validate the results by directly parsing the generated solution (.sln). Co-Author: Leonid Yurchenko <nocturne@qarea.com>
2012-04-19 16:35:10 +04:00
endif()
file: Add GENERATE command to produce files at generate time The idea is to write to a temp file which contains generator expressions, and at generate time, evaluate the generator expressions, and write the result to a file. Because executables on Windows are limited in the length of command line it is possible to use, it is common to write command line arguments to a file instead and specify the file as a source of arguments. This new FILE(GENERATE) subcommand allows the use of generator expressions to create such files so that they can be used with add_custom_command for example.
2013-01-02 20:10:04 +04:00
Xcode: Add source file property to control file type (#14854) Add source file properties to control Xcode file type attributes: XCODE_EXPLICIT_FILE_TYPE => explicitFileType XCODE_LAST_KNOWN_FILE_TYPE => lastKnownFileType Add a RunCMake.XcodeProject test to verify generated project content.
2014-05-15 21:50:53 +04:00
if(XCODE_VERSION AND NOT "${XCODE_VERSION}" VERSION_LESS 3)
OS X: Add platform-specific Frameworks search path Otherwise find_library is unable to lookup the XCTest framework which is not located in the SDK serach path: In the 10.10 SDK the SDK frameworks are located here: $DEVELOPER_DIR/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/System/Library/Frameworks whereas the Platform SDKs are located here: $DEVELOPER_DIR/Platforms/MacOSX.platform/Developer/Library/Frameworks Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
2015-02-22 21:00:11 +03:00
add_RunCMake_test(XcodeProject -DXCODE_VERSION=${XCODE_VERSION})
Xcode: Add source file property to control file type (#14854) Add source file properties to control Xcode file type attributes: XCODE_EXPLICIT_FILE_TYPE => explicitFileType XCODE_LAST_KNOWN_FILE_TYPE => lastKnownFileType Add a RunCMake.XcodeProject test to verify generated project content.
2014-05-15 21:50:53 +04:00
endif()
file: Add GENERATE command to produce files at generate time The idea is to write to a temp file which contains generator expressions, and at generate time, evaluate the generator expressions, and write the result to a file. Because executables on Windows are limited in the length of command line it is possible to use, it is common to write command line arguments to a file instead and specify the file as a source of arguments. This new FILE(GENERATE) subcommand allows the use of generator expressions to create such files so that they can be used with add_custom_command for example.
2013-01-02 20:10:04 +04:00
add_RunCMake_test(File_Generate)
export: Error when exporting a target without a language First, it prevents a NULL dereference and second it reiterates that targets without languages are not supported by CMake. Add a RunCMake.ExportWithoutLanguage test exporting a library without a languages.
2013-07-23 01:25:21 +04:00
add_RunCMake_test(ExportWithoutLanguage)
target_link_libraries: Add PUBLIC/PRIVATE/INTERFACE keyword signature Add a new signature to help populate INTERFACE_LINK_LIBRARIES and LINK_LIBRARIES cleanly in a single call. Add policy CMP0023 to control whether the keyword signatures can be mixed with uses of the plain signatures on the same target.
2013-06-04 18:21:33 +04:00
add_RunCMake_test(target_link_libraries)
Add target_compile_features command. This can be used to set the compiler features required by particular targets. An error is issued at CMake time if the compiler does not support the required feature. If a language dialect flag is required by the features used, that will be added automatically. Base the target_compile_features command on cmTargetPropCommandBase. This gives us 'free' handling of IMPORTED, ALIAS, INTERFACE, non-compilable and missing targets.
2013-10-13 16:25:08 +04:00
Tests: Run RunCMake.target_compile_features unconditionally. It is so far testing only cases which are fatal regardless of recorded features.
2014-04-16 19:20:15 +04:00
add_RunCMake_test(target_compile_features)
CheckStructHasMember: Add support for C++ Previously if headers required to check if a struct has a member can be compiled with C++ compiler only, the check would fail because the C compiler fails. As a consequence, the result variable would be set to false, even if the struct has that particular member. Teach CHECK_STRUCT_HAS_MEMBER to accept a new optional argument LANGUAGE that allows one to explicitly set the compiler to use. The new signature is therefore: CHECK_STRUCT_HAS_MEMBER (<struct> <member> <header> <variable> [LANGUAGE <language>])
2013-09-20 17:10:40 +04:00
add_RunCMake_test(CheckModules)
cmake: Improve '-E create_symlink' edge case handling (#14713) The logic added by commit ffc0b5e4 (Overwrite the symlink if it already exists, 2007-02-15) does not recognize and remove existing broken links before replacing them. Improve the logic to remove any existing destination file or link (but not directory). On failure, report an error message explaining why the existing path could not be removed or the new one could not be created. Add a RunCMake.CommandLine test to cover 'cmake -E' cases. Start with test cases covering 'cmake -E create_symlink' behavior on UNIX platforms.
2014-01-20 22:50:31 +04:00
add_RunCMake_test(CommandLine)
Tests: Consolidate, refactor and extend -E tar tests
2015-04-07 20:40:33 +03:00
add_RunCMake_test(CommandLineTar)
InstallRules: added new variable to disable generation of install rules The boolean variable CMAKE_SKIP_INSTALL_RULES allows disabling generation of install rules for projects which don't want them.
2013-12-25 20:59:24 +04:00
add_RunCMake_test(install)
CPack generator independent tests CPackConfig.cmake file generation from CMake test suite. Currently it contains only a simple test without special characters in variable value. Test is not part of RunCMake/CPack as those tests are expected to be run for a specified generator.
2015-08-28 09:07:52 +03:00
add_RunCMake_test(CPackConfig)
Add an "installed file" property scope Teach set_property and get_property an "INSTALL" property type to be associated with install-tree file paths. Make the properties available to CPack for use during packaging. Add a "prop_inst" Sphinx domain object type for documentation of such properties.
2014-05-15 21:12:40 +04:00
add_RunCMake_test(CPackInstallProperties)
ExternalProject: Add unit tests for CMAKE_CACHE_DEFAULT_ARGS
2014-10-28 13:05:57 +03:00
add_RunCMake_test(ExternalProject)
ctest: Add a new --repeat-until-fail option This option tells ctest to run each test N times until the test fails or the N times have run. This is useful for finding random failing tests.
2015-03-06 00:51:10 +03:00
add_RunCMake_test(CTestCommandLine)
Tests: Add case for CPack source package with symlinks
2015-03-31 22:04:39 +03:00
# Only run this test on unix platforms that support
# symbolic links
if(UNIX)
add_RunCMake_test(CPackSymlinks)
endif()
Tests: Run IfacePaths tests with a parameter. Run the tests for the INCLUDE_DIRECTORIES INTERFACE property in a specific build location, and update the stderr expectation to match the new output.
2014-11-30 15:42:00 +03:00
set(IfacePaths_INCLUDE_DIRECTORIES_ARGS -DTEST_PROP=INCLUDE_DIRECTORIES)
add_RunCMake_test(IfacePaths_INCLUDE_DIRECTORIES TEST_DIR IfacePaths)
CPackRPM: Allow multiple path relocation prefixes for one package
2015-01-21 02:29:46 +03:00
Allow export of targets with INTERFACE_SOURCES. Use the same rules for paths in source and binary dirs in installed INTERFACE_SOURCES as are used for INTERFACE_INCLUDE_DIRECTORIES.
2014-11-28 20:58:38 +03:00
set(IfacePaths_SOURCES_ARGS -DTEST_PROP=SOURCES)
add_RunCMake_test(IfacePaths_SOURCES TEST_DIR IfacePaths)
Genex: Enable use of COMPILE_LANGUAGE for compile options. Follow-ups will allow the use of the generator expression for compile definitions and include directories for non-IDE generators.
2014-11-26 00:47:44 +03:00
add_RunCMake_test(COMPILE_LANGUAGE-genex)
FindMatlab: Rewrite module and provide a usage API Implement a brand new FindMatlab module: - Add support for versions and components. - Find Matlab and its version in a more precise and multiplatform way. - Add API to create a new mex extension with documentation. - Add API to add matlab unit tests (with or without the unit test framework). - Find as much as possible based on a single Matlab_ROOT_DIR cache entry and allow the user to change it to re-find everything.
2015-02-12 19:13:31 +03:00
# Matlab module related tests
if(CMake_TEST_FindMatlab)
add_RunCMake_test(FindMatlab)
endif()
Properties: Add CROSSCOMPILING_EMULATOR target property. Add CROSSCOMPILING_EMULATOR target property for executables. This is used by subsequent patches to run exectuables created for the target system when crosscompiling. The property is initialized by the CMAKE_CROSSCOMPILING_EMULATOR variable when defined.
2015-03-24 07:02:50 +03:00
add_executable(pseudo_emulator pseudo_emulator.c)
add_RunCMake_test(CrosscompilingEmulator
-DPSEUDO_EMULATOR=$<TARGET_FILE:pseudo_emulator>)
Tests: Create pseudo_emulator output dir for Xcode 2.x Apply the workardound from commit v2.8.2~598 (Create CMakeLibTests output dir for Xcode, 2009-12-09) to the pseudo_emulator tool.
2015-04-10 19:42:49 +03:00
# Xcode 2.x forgets to create the output directory before linking
# the individual architectures.
if(CMAKE_OSX_ARCHITECTURES AND XCODE AND NOT "${XCODE_VERSION}" MATCHES "^[^12]")
add_custom_command(
TARGET pseudo_emulator
PRE_BUILD COMMAND ${CMAKE_COMMAND} -E make_directory "${CMAKE_CFG_INTDIR}"
)
endif()
Add options to run include-what-you-use with the compiler Create a <LANG>_INCLUDE_WHAT_YOU_USE target property (initialized by a CMAKE_<LANG>_INCLUDE_WHAT_YOU_USE variable) to specify an IWYU command line to be run along with the compiler.
2015-05-18 21:39:25 +03:00
if("${CMAKE_GENERATOR}" MATCHES "Make|Ninja")
add_executable(pseudo_iwyu pseudo_iwyu.c)
add_RunCMake_test(IncludeWhatYouUse -DPSEUDO_IWYU=$<TARGET_FILE:pseudo_iwyu>)
Add options to launch the compiler through tools like ccache or distcc Create a <LANG>_COMPILER_LAUNCHER target property (initialized by a CMAKE_<LANG>_COMPILER_LAUNCHER variable) to specify a compiler launcher tool. This will supersede the CMAKE_<LANG>_COMPILER_ARG1 approach to using such tools. The old approach set CMAKE_<LANG>_COMPILER to the launcher tool while the new approach leaves this variable set to the actual compiler. Implement this property for Makefile and Ninja generators. It cannot be implemented for VS or Xcode generators as the IDE build tools offer no such hooks.
2015-06-04 22:56:56 +03:00
add_RunCMake_test(CompilerLauncher)
Add options to run include-what-you-use with the compiler Create a <LANG>_INCLUDE_WHAT_YOU_USE target property (initialized by a CMAKE_<LANG>_INCLUDE_WHAT_YOU_USE variable) to specify an IWYU command line to be run along with the compiler.
2015-05-18 21:39:25 +03:00
endif()
Tests: Add RunCMake tests for CPack{Deb,RPM} Add script structure for easier addition of new CPack related tests.
2015-06-05 22:03:26 +03:00
add_RunCMake_test_group(CPack "DEB;RPM")
Windows: Optionally generate DLL module definition files automatically Create target property WINDOWS_EXPORT_ALL_SYMBOLS to automatically generate a module definition file from MS-compatible .obj files and give it to the linker in order to export all symbols from the .dll part of a SHARED library.
2015-06-19 23:12:43 +03:00
# add a test to make sure symbols are exported from a shared library
# for MSVC compilers CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS property is used
add_RunCMake_test(AutoExportDll)