summaryrefslogtreecommitdiffstats
path: root/Tests/RunCMake/configure_file/RerunCMake-stdout.txt
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2015-01-23 15:02:04 (GMT)
committerBrad King <brad.king@kitware.com>2015-01-27 16:18:37 (GMT)
commit7f2dc8dc54fa6486423477dd673725bc40d3fdeb (patch)
tree191f5668ce864732a32acc151bbc5c074085d088 /Tests/RunCMake/configure_file/RerunCMake-stdout.txt
parentdaf95a38277f4c732987933a63143dde77dd0a10 (diff)
downloadCMake-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-stdout.txt')
-rw-r--r--Tests/RunCMake/configure_file/RerunCMake-stdout.txt3
1 files changed, 3 insertions, 0 deletions
diff --git a/Tests/RunCMake/configure_file/RerunCMake-stdout.txt b/Tests/RunCMake/configure_file/RerunCMake-stdout.txt
new file mode 100644
index 0000000..34c873c
--- /dev/null
+++ b/Tests/RunCMake/configure_file/RerunCMake-stdout.txt
@@ -0,0 +1,3 @@
+-- Configuring done
+-- Generating done
+-- Build files have been written to: .*/Tests/RunCMake/configure_file/RerunCMake-build