At 04:51 PM 6/29/2006, Scott Amort wrote: >William A. Hoffman wrote: >> make test should do the trick. >> You can also run ctest directly in the build tree. >> What you have should work. You might have to move the >> ENABLE_TESTING to the top of the project. Also you can >> look for the DartTesting. You can look for this file >> in your build tree and make sure it looks good: >> DartTestfile.txt > >Thanks Bill - I just needed to move ENABLE_TESTING up to the project >root. Works now! > >However, it does compile the testing executables during the `make' >command, and only runs them during the `make test'. If I make a change >to one of the tests, I have to run `make' again, then `make test'... >`make test' alone doesn't see that changes were made to the sources. >Certainly only a minor complaint, but is there a way to restrict the >compiling/link/executing of tests to the `make test' command?
You may want to look at the ctest --build-and-test option. We use it in cmake itself. It will run cmake and do a build on a test that is not include in the parent build tree. -Bill _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake