Well, foo. Turns out CTEST_CUSTOM_PRE_TEST behaves differently than I expected. If you run ctest in a subdirectory, CTestCustom.cmake isn't executed. So the top-level one isn't inherited by the subdirectories, as it were.
Are we supposed to have a copy of CTestCustom.cmake in each project? Which ones get run when? On Fri, Sep 12, 2014 at 1:34 PM, Dan Kegel <[email protected]> wrote: > I'm porting a large project with many subdirectories from autotools to > cmake and ctest. > It's going well, but I ran into a question on how to do test setup/teardown. > I've got CTEST_CUSTOM_PRE_TEST working nicely, but now I need different > conditions for each directory's worth of tests. Is there anything like > CTEST_CUSTOM_PRE_TEST that gets run at the beginning of each subprojects' > tests? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
