kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
CMake/Tests/RunCMake/BuildDepends/RunCMakeTest.cmake

89 lines
3.1 KiB
CMake
Raw Normal View History

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
include(RunCMake)
Tests: Fix RunCMake.BuildDepends filesystem delay for Watcom WMake Our 1.125s delay does not seem to be long enough to be reliable with the Watcom `wmake` tool. Use a longer delay for Watcom.
2016-04-29 18:47:35 +03:00
if(RunCMake_GENERATOR STREQUAL "Borland Makefiles" OR
RunCMake_GENERATOR STREQUAL "Watcom WMake")
Tests: Fix RunCMake.BuildDepends filesystem delay for Borland Makefiles Our 1.125s delay does not seem to be long enough to be reliable with the Borland "make" tool. Use a longer delay for Borland.
2015-09-25 16:10:37 +03:00
set(fs_delay 3)
else()
set(fs_delay 1.125)
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
function(run_BuildDepends CASE)
# Use a single build tree for a few tests without cleaning.
set(RunCMake_TEST_BINARY_DIR ${RunCMake_BINARY_DIR}/${CASE}-build)
set(RunCMake_TEST_NO_CLEAN 1)
if(RunCMake_GENERATOR MATCHES "Make|Ninja")
set(RunCMake_TEST_OPTIONS -DCMAKE_BUILD_TYPE=Debug)
endif()
file(REMOVE_RECURSE "${RunCMake_TEST_BINARY_DIR}")
file(MAKE_DIRECTORY "${RunCMake_TEST_BINARY_DIR}")
include(${RunCMake_SOURCE_DIR}/${CASE}.step1.cmake OPTIONAL)
run_cmake(${CASE})
set(RunCMake-check-file check.cmake)
set(check_step 1)
run_cmake_command(${CASE}-build1 ${CMAKE_COMMAND} --build . --config Debug)
Add support for *.manifest source files with MSVC tools Classify .manifest sources separately, add dependencies on them, and pass them to the MS manifest tool to merge with linker-generated manifest files. Inspired-by: Gilles Khouzam <gillesk@microsoft.com>
2015-09-16 17:24:16 +03:00
if(run_BuildDepends_skip_step_2)
return()
endif()
Tests: Fix RunCMake.BuildDepends filesystem delay for Borland Makefiles Our 1.125s delay does not seem to be long enough to be reliable with the Borland "make" tool. Use a longer delay for Borland.
2015-09-25 16:10:37 +03:00
execute_process(COMMAND ${CMAKE_COMMAND} -E sleep ${fs_delay}) # handle 1s resolution
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
include(${RunCMake_SOURCE_DIR}/${CASE}.step2.cmake OPTIONAL)
set(check_step 2)
run_cmake_command(${CASE}-build2 ${CMAKE_COMMAND} --build . --config Debug)
endfunction()
run_BuildDepends(C-Exe)
Drop Visual Studio 6 generator This generator has been deprecated since CMake 3.3. Remove it. Update documentation, modules, and tests to drop content specific to this generator.
2016-03-09 17:42:18 +03:00
if(NOT RunCMake_GENERATOR MATCHES "Visual Studio 7|Xcode")
Add support for *.manifest source files with MSVC tools Classify .manifest sources separately, add dependencies on them, and pass them to the MS manifest tool to merge with linker-generated manifest files. Inspired-by: Gilles Khouzam <gillesk@microsoft.com>
2015-09-16 17:24:16 +03:00
if(RunCMake_GENERATOR MATCHES "Visual Studio 10")
# VS 10 forgets to re-link when a manifest changes
set(run_BuildDepends_skip_step_2 1)
endif()
run_BuildDepends(C-Exe-Manifest)
unset(run_BuildDepends_skip_step_2)
endif()
Ninja: Always re-run custom commands that have symbolic dependencies If a custom command has a SYMBOLIC output (that is never actually created) then do not mark the custom command build statement as 'restat'. Otherwise other custom commands that depend on the symbolic output may not always re-run because after running the first custom command Ninja 'restat' will detect that the output timestamp did not change and skip its dependents. This was observed with the ExternalProject BUILD_ALWAYS option where Ninja would not re-run the 'install' step each time 'build' re-runs.
2015-11-19 23:13:11 +03:00
Ninja: Restat custom command byproducts even with a SYMBOLIC output (#16049) The change in commit v3.5.0-rc1~198^2 (Ninja: Always re-run custom commands that have symbolic dependencies, 2015-11-19) broke the byproducts feature added by commit v3.2.0-rc1~340^2~2 (Add an option for explicit BYPRODUCTS of custom commands, 2014-11-13) when SYMBOLIC outputs also appear. This case occurs with AUTORCC-generated custom targets because the output is SYMBOLIC (to always run) and the generated file is a byproduct (for restat so dependents do not run unnecessarily). The two use cases conflict because Ninja does not support per-output restat. Favor restat whenever byproducts are present because it is required for byproducts to work correctly. In use cases where we want an always-run chain we simply will not be able to also use byproducts.
2016-04-05 23:20:28 +03:00
run_BuildDepends(Custom-Symbolic-and-Byproduct)
Ninja: Always re-run custom commands that have symbolic dependencies If a custom command has a SYMBOLIC output (that is never actually created) then do not mark the custom command build statement as 'restat'. Otherwise other custom commands that depend on the symbolic output may not always re-run because after running the first custom command Ninja 'restat' will detect that the output timestamp did not change and skip its dependents. This was observed with the ExternalProject BUILD_ALWAYS option where Ninja would not re-run the 'install' step each time 'build' re-runs.
2015-11-19 23:13:11 +03:00
run_BuildDepends(Custom-Always)
Xcode: ReRunCMake even if files disappeared (#15992)
2016-03-06 19:46:53 +03:00
Tests: Add test for CMAKE_DEPENDS_IN_PROJECT_ONLY variable
2016-03-22 23:03:28 +03:00
if(RunCMake_GENERATOR MATCHES "Make" AND
NOT "${RunCMake_BINARY_DIR}" STREQUAL "${RunCMake_SOURCE_DIR}")
run_BuildDepends(MakeInProjectOnly)
endif()
Xcode: ReRunCMake even if files disappeared (#15992)
2016-03-06 19:46:53 +03:00
function(run_ReGeneration)
# test re-generation of project even if CMakeLists.txt files disappeared
# Use a single build tree for a few tests without cleaning.
set(RunCMake_TEST_BINARY_DIR ${RunCMake_BINARY_DIR}/regenerate-project-build)
set(RunCMake_TEST_SOURCE_DIR ${RunCMake_BINARY_DIR}/regenerate-project-source)
set(RunCMake_TEST_NO_CLEAN 1)
file(REMOVE_RECURSE "${RunCMake_TEST_BINARY_DIR}")
file(REMOVE_RECURSE "${RunCMake_TEST_SOURCE_DIR}")
set(ProjectHeader [=[
cmake_minimum_required(VERSION 3.5)
project(Regenerate-Project NONE)
]=])
# create project with subdirectory
file(WRITE "${RunCMake_TEST_SOURCE_DIR}/CMakeLists.txt" "${ProjectHeader}"
"add_subdirectory(mysubdir)")
file(MAKE_DIRECTORY "${RunCMake_TEST_SOURCE_DIR}/mysubdir")
file(WRITE "${RunCMake_TEST_SOURCE_DIR}/mysubdir/CMakeLists.txt" "# empty")
run_cmake(Regenerate-Project)
execute_process(COMMAND ${CMAKE_COMMAND} -E sleep ${fs_delay})
# now we delete the subdirectory and adjust the CMakeLists.txt
file(REMOVE_RECURSE "${RunCMake_TEST_SOURCE_DIR}/mysubdir")
file(WRITE "${RunCMake_TEST_SOURCE_DIR}/CMakeLists.txt" "${ProjectHeader}")
run_cmake_command(Regenerate-Project-Directory-Removed
${CMAKE_COMMAND} --build "${RunCMake_TEST_BINARY_DIR}")
unset(RunCMake_TEST_BINARY_DIR)
unset(RunCMake_TEST_SOURCE_DIR)
unset(RunCMake_TEST_NO_CLEAN)
endfunction()
if(RunCMake_GENERATOR STREQUAL "Xcode")
run_ReGeneration(regenerate-project)
endif()