d91f66acab
The previous behavior of the pyexpander check (in VTKmCheckPyexpander.cmake) was to generate the file in the binary directory and then remove it from there iff the check failed. This caused two problems. The first is that if the check failed then the file was deleted and there was no file to copy to the source as the instructions suggested. The second is that if the check succeeded the build would then use the files in the build directory rather than the source directory, and if the programmer accidently modified the binary files (because, for example, if a build error occured there), the configure system would not catch that. This change in behavior was that if the check failed, the file is renamed to have a .save extension so that the file remains and can be easily copied back to the source directory if that is appropriate. If the check succeeds, the generated file is removed and a file with the extension .check is touched. That .check file is used as a make target to signal that the test has been performed. |
||
---|---|---|
.. | ||
CheckCXX11Features | ||
CheckCXX11Features.cmake | ||
FindBoostHeaders.cmake | ||
FindPyexpander.cmake | ||
TestBuild.cxx.in | ||
VTKmCheckCopyright.cmake | ||
VTKmCheckPyexpander.cmake | ||
VTKmCompilerExtras.cmake | ||
VTKmConfig.cmake.in | ||
VTKmConfigVersion.cmake.in | ||
VTKmCopyrightStatement.txt | ||
VTKmMacros.cmake | ||
VTKmSystemInformation.cmake |