Go to file
Kenneth Moreland d91f66acab Keep pyexpander generated files out of build directory
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.
2014-10-08 10:03:10 -06:00
CMake Keep pyexpander generated files out of build directory 2014-10-08 10:03:10 -06:00
docs revise the header guard naming convention to not conflict with macro names. 2014-03-07 10:22:36 -05:00
vtkm Add exception for timing test with MSVC in non-release mode. 2014-09-15 14:23:38 -06:00
CMakeLists.txt Add SystemInformation test 2014-09-10 13:36:16 -06:00
CTestConfig.cmake Add the correct copyright statement to CTestConfig. 2014-06-30 11:21:07 -04:00
LICENSE.txt Add a license to vtkm. 2014-02-10 15:00:17 -05:00
README.md Update readme to include PISTON. 2014-07-16 10:15:44 -06:00