The closest I've come to solving this problem is that for each test
${testTarget}, I add two cmake tests:
add_test(NAME build_${testTarget} COMMAND ${CMAKE_COMMAND} --build
${CMAKE_BINARY_DIR} --target ${testTarget} --config
$CONFIGURATION)
add_test(NAME someName COMMAND ${testTarget} ...)
It
So you run 'ctest -R testTarget' and it picks up the build test too?
Hmm. Thanks.
On Wed, 9 May 2012, Petr Kmoch wrote:
The closest I've come to solving this problem is that for each test
${testTarget}, I add two cmake tests:
add_test(NAME build_${testTarget} COMMAND ${CMAKE_COMMAND}
Actuall, I haven't tried this using ctest directly, just via make test
(or its Visual Studio equivalent). I believe that to make it work as
one test, you'd have to provide a trivial launcher which does the two
build - run steps in sequence.
Petr
On Wed, May 9, 2012 at 3:16 PM, Leif Walsh
I assume you have looked at ctest --build-and-test?
-Bill
--
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
Yeah, I tried it and I couldn't really figure out what it's doing. I could give
it a binary name that it would build and I could give it a command to use to
test, but the goal here is to only require the test name (since that may be
different from the binary name) and to build all dependencies
On Mon, May 7, 2012 at 7:27 PM, Leif Walsh leif.wa...@gmail.com wrote:
Hi,
Is there a make, cmake, or ctest way to rebuild the dependencies of a
test if needed, and then run the test?
No -- there is no knowledge in the generated build system about what a
test depends on. The only thing
Hi,
Is there a make, cmake, or ctest way to rebuild the dependencies of a
test if needed, and then run the test?
Suppose I have a bulit directory and I'm developing. I want to make
edits, then run a command specifying one test to check, so that
anything needed by that test gets rebuilt (if my
