kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
CMake/Tests/EnforceConfig.cmake.in

27 lines
1.0 KiB
CMake
Raw Normal View History

Always use a configuration for CTestTestTimeout This test requires that the dashboard script it drives be invoked with "ctest -C <config> -S ...". We create a "CTestTest_CONFIG" variable to hold a configuration selected at test time. We use the configuration given to the outer CTest, if any, and then default to either Debug or the CMAKE_BUILD_TYPE.
2009-12-01 17:12:07 +03:00
# Choose a configuration with which to drive CTest tests.
IF(CTEST_CONFIGURATION_TYPE)
SET(CTestTest_CONFIG "${CTEST_CONFIGURATION_TYPE}")
ELSE(CTEST_CONFIGURATION_TYPE)
SET(CTestTest_CONFIG "@CTestTest_CONFIG@")
ENDIF(CTEST_CONFIGURATION_TYPE)
Always use a configuration for CMake tests Previously our EnforceConfig script that loads at test-time would only enforce a non-empty CTEST_CONFIGURATION_TYPE for CMake 2.6.2 and lower. Now we simply always enforce use of a configuration, and select one of the configurations that was built if none is given. This is necessary to run tests like CMake.Install that need to know the configuration with which CMake was built.
2009-12-10 19:19:23 +03:00
# Choose a configuration that was built if none is given.
IF(NOT CTEST_CONFIGURATION_TYPE)
ENH: Re-enable new 'testing' test mode This fixes selection of a configuration when none is specified to find an available configuration of the ctest test-command.
2009-01-05 22:14:25 +03:00
SET(CTEST_CMD "@CMAKE_CTEST_COMMAND@@CMAKE_EXECUTABLE_SUFFIX@")
GET_FILENAME_COMPONENT(CTEST_DIR "${CTEST_CMD}" PATH)
GET_FILENAME_COMPONENT(CTEST_EXE "${CTEST_CMD}" NAME)
FOREACH(cfg Release Debug MinSizeRel RelWithDebInfo)
IF(NOT CTEST_CONFIGURATION_TYPE)
IF(EXISTS "${CTEST_DIR}/${cfg}/${CTEST_EXE}")
SET(CTEST_CONFIGURATION_TYPE ${cfg})
ENDIF(EXISTS "${CTEST_DIR}/${cfg}/${CTEST_EXE}")
ENDIF(NOT CTEST_CONFIGURATION_TYPE)
ENDFOREACH(cfg)
IF(NOT CTEST_CONFIGURATION_TYPE)
SET(CTEST_CONFIGURATION_TYPE NoConfig)
ENDIF(NOT CTEST_CONFIGURATION_TYPE)
MESSAGE("Guessing configuration ${CTEST_CONFIGURATION_TYPE}")
Always use a configuration for CMake tests Previously our EnforceConfig script that loads at test-time would only enforce a non-empty CTEST_CONFIGURATION_TYPE for CMake 2.6.2 and lower. Now we simply always enforce use of a configuration, and select one of the configurations that was built if none is given. This is necessary to run tests like CMake.Install that need to know the configuration with which CMake was built.
2009-12-10 19:19:23 +03:00
ENDIF(NOT CTEST_CONFIGURATION_TYPE)
Fake $HOME to isolate tests from user On platforms with $HOME in the environment, some of our features use it to store information in the user home directory. However, tests for these features should not touch the real user home directory. Instead we configure a fake $HOME that points inside the build tree for use during testing. See issue #9949.
2009-11-23 22:24:53 +03:00
Improve fake $HOME test isolation code The commit "Fake $HOME to isolate tests from user" started setting $HOME in the CTest script environment. On some platforms tests depend on some local configuration in the home directory, such as the "cvs login" for KWSys in CTestTest3. In this commit we now construct a fake home dir during CMake config step and populate it with a .cvspass file needed by the test. We also check CTEST_NO_TEST_HOME to optionally disable the test home. See issue #9949.
2009-11-24 20:15:33 +03:00
@TEST_HOME_ENV_CODE@