diff options
| author | Robert Maynard <robert.maynard@kitware.com> | 2013-09-03 19:31:12 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2013-09-09 14:58:21 (GMT) |
| commit | 38571f2c9446343a652cfdccea636028abd9f7aa (patch) | |
| tree | 4424f3f80f76e37e56a39e59242387e402aaf724 /Tests/Tutorial/Step2/MathFunctions/MathFunctions.h | |
| parent | 0264eec9d32200c692ddfb756871ac4a4465863c (diff) | |
| download | CMake-38571f2c9446343a652cfdccea636028abd9f7aa.zip CMake-38571f2c9446343a652cfdccea636028abd9f7aa.tar.gz CMake-38571f2c9446343a652cfdccea636028abd9f7aa.tar.bz2 | |
cmMakefile: Do not track CMake temporary files.
Since commit ad502502 (cmMakefile: Track configured files so we can
regenerate them, 2013-06-18) cmMakefile::ConfigureFile records the
configured file as an output file generated by CMake. The intention is
that for make and ninja we can re-run CMake when one of the files it
generates goes missing. However, files configured temporarily in
CMakeTmp directories by Check* modules do not live past the CMake
invocation.
We have to also track input files to the configure command. In theory
the input to a configure command could it self be a file that is going
to be deleted later (output from a custom command or configure_file).
Diffstat (limited to 'Tests/Tutorial/Step2/MathFunctions/MathFunctions.h')
0 files changed, 0 insertions, 0 deletions