EXECUTABLE_OUTPUT_PATH for tests
Andreas Pakulat
apaku at gmx.de
Fri Sep 21 12:13:32 CEST 2007
On 20.09.07 18:43:25, Alexander Neundorf wrote:
> Two more notes:
> to run tests (i.e. added via ADD_TEST) it is not necessary to know where the
> executable is located. You can run the tests via ctest:
> $ ctest <- runs all tests in this dir and below
> $ ctest -R kio <- runs all tests whose name match .*kio.*
> There are more options like this.
Ok, that should be advertised, especially the ctest -V -R <test> method
to see the output from the tests so one knows which tests fail.
> I understand you this way that we remove the side effect now and put the
> EXECUTABLE_OUTPUT_PATH in the cmake files back -> no side effect, tests are
> in the current dir, everybody sees what's going on.
>
> But where do you see a problem with putting the SET_TARGET_PROPERTIES() call
> which sets the individual output path in the macro now ?
I don't see any problem with putting the EXECUTABLE_OUTPUT_PATH back
into the CMake files and also setting the target property. I never said
that and I certainly never meant to imply that.
Andreas
--
You have the capacity to learn from mistakes. You'll learn a lot today.
More information about the Kde-buildsystem
mailing list