vtk-m/vtkm/internal
Kenneth Moreland adad702652 If pyexpander is available, run it and check the source file.
Although we cannot expect every developer to have pyexpander, for those
that do the build will automatically run it and check the expanded file
in the source code. If they match, a descriptive error is given.

We don't automatically update the file because subtle problems might
occur. It is better to alert a developer to fix the problem properly.
2014-06-26 18:26:45 -06:00
..
testing Fix testing versions. 2014-06-11 10:45:36 -06:00
CMakeLists.txt If pyexpander is available, run it and check the source file. 2014-06-26 18:26:45 -06:00
Configure.h.in revise the header guard naming convention to not conflict with macro names. 2014-03-07 10:22:36 -05:00
ConfigureFor32.h Make sure all header wrapper macros start with vtk_m_ rather than vtkm_ 2014-06-11 10:43:36 -06:00
ConfigureFor64.h Make sure all header wrapper macros start with vtk_m_ rather than vtkm_ 2014-06-11 10:43:36 -06:00
ExportMacros.h Make sure all header wrapper macros start with vtk_m_ rather than vtkm_ 2014-06-11 10:43:36 -06:00
FunctionInterface.h Replace Boost preprocessor iteration with macro expansion tool 2014-06-25 16:03:44 -06:00
FunctionInterfaceDetailPost.h Replace Boost preprocessor iteration with macro expansion tool 2014-06-25 16:03:44 -06:00
FunctionInterfaceDetailPost.h.in Replace Boost preprocessor iteration with macro expansion tool 2014-06-25 16:03:44 -06:00
FunctionInterfaceDetailPre.h Replace Boost preprocessor iteration with macro expansion tool 2014-06-25 16:03:44 -06:00
FunctionInterfaceDetailPre.h.in Replace Boost preprocessor iteration with macro expansion tool 2014-06-25 16:03:44 -06:00