Taking a page from the CMake project itself, I'm trying to separate tests into
their own sub-builds. (Because of the highly regular nature of our unit tests,
these sub-builds are dynamically generated by the main build. That's not
relevant to my issue, I'm just bragging and sowing ideas :P)
In the main project, I've done ADD_TEST which uses ctest as the command -
almost identical to the CMake project itself!
ADD_TEST(${name}_test ${CMAKE_CTEST_COMMAND}
-VV
--build-and-test
"${CMAKE_CURRENT_SOURCE_DIR}/tests/"
"${CMAKE_CURRENT_BINARY_DIR}/tests/"
#--build-two-config
--build-config ${CMAKE_BUILD_TYPE}
--build-generator ${CMAKE_TEST_GENERATOR}
--build-makeprogram ${CMAKE_TEST_MAKEPROGRAM}
--build-project ${parent}
--build-target ${name}_test
#--test-command ${name}_test
--test-command ${CMAKE_CTEST_COMMAND} -V ${name}_test
)
But despite the -VV (AND the -V in the --test-command, that's an artifact of me
trying everything I could think of) I only get the summary output.
I'm an inch away from stepping through my own build of CTest, but figured I'd
write before spending copious amounts of time staring at code I don't know.
Ideas? Am I even following the right idiom? I really would like developers to
be able to see why their test failed - did it fail to build? Actual test
failure? Running ctest manually in the build folder works, but that's not gonna
please the IDE devs.
+ poppy
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
