diff options
| author | Brad King <brad.king@kitware.com> | 2015-01-23 15:02:04 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2015-01-27 16:18:37 (GMT) |
| commit | 7f2dc8dc54fa6486423477dd673725bc40d3fdeb (patch) | |
| tree | 191f5668ce864732a32acc151bbc5c074085d088 /Tests/RunCMake/configure_file/RerunCMake.cmake | |
| parent | daf95a38277f4c732987933a63143dde77dd0a10 (diff) | |
| download | CMake-7f2dc8dc54fa6486423477dd673725bc40d3fdeb.zip CMake-7f2dc8dc54fa6486423477dd673725bc40d3fdeb.tar.gz CMake-7f2dc8dc54fa6486423477dd673725bc40d3fdeb.tar.bz2 | |
configure_file: Test that CMake re-runs on input change or output missing
With the Makefile generators we expect that touching or modifying the
input file of a configure_file, or removing its output, will cause CMake
to re-run on the next build. Extend the RunCMake.configure_file test
with a case covering this. Also check that CMake does not re-run if
nothing has changed.
Diffstat (limited to 'Tests/RunCMake/configure_file/RerunCMake.cmake')
| -rw-r--r-- | Tests/RunCMake/configure_file/RerunCMake.cmake | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/Tests/RunCMake/configure_file/RerunCMake.cmake b/Tests/RunCMake/configure_file/RerunCMake.cmake new file mode 100644 index 0000000..890cc1f --- /dev/null +++ b/Tests/RunCMake/configure_file/RerunCMake.cmake @@ -0,0 +1,8 @@ +message("Running CMake on RerunCMake") # write to stderr if cmake reruns +configure_file( + "${CMAKE_CURRENT_BINARY_DIR}/ConfigureFileInput.txt.in" + "${CMAKE_CURRENT_BINARY_DIR}/ConfigureFileOutput.txt" + @ONLY + ) +# make sure CMakeCache.txt is newer than ConfigureFileOutput.txt +execute_process(COMMAND ${CMAKE_COMMAND} -E sleep 1) |