On 05/06/2015 02:32 PM, Ben Boeckel wrote: > I really question the old behavior at all (it's not like it made things > magically "work"), but OK :/ . I'd be OK with replacing it with `-k` > without a policy though (it does the same thing but makes the exit > code...useful).
IIRC when use of -i was introduced we actually used -k first and found it to be inadequate for the needs at the time. Since requirements seem to have changed I think switching to -k is okay. > Heh. We were setting MAKECOMMAND, but using ctest_build. Seems the > documentation could use some sprucing up :) . See the "MakeCommand" setting here: http://www.cmake.org/cmake/help/v3.2/manual/ctest.1.html#ctest-build-step It explains both CTEST_BUILD_COMMAND and MAKECOMMAND. What is missing is that ctest_build docs: http://www.cmake.org/cmake/help/v3.2/command/ctest_build.html should reference CTEST_BUILD_COMMAND. Please add that. Thanks, -Brad -- 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-developers
