Re: [CMake] Establishing TDD workflow

2008-11-30 Thread Bill Hoffman
Alexander Neundorf wrote: Usually you do: add_executable(ut TestUnittest.cpp stdafx.cpp SomeSuite.cpp SecondSuite.cpp) target_link_libraries(ut UnitTest++.vsnet2008) add_test(ut_test ut) And then expect the developer to do a "make test" or "ctest" after building the pro

Re: [CMake] Establishing TDD workflow

2008-11-30 Thread Alexander Neundorf
On Sunday 30 November 2008, Slava Tutushkin wrote: > Hi all, > > I'm only starting with cmake, so my question can be quite lame. > However, I have read the "Mastering Cmake" and googled a lot about it > already. > > I have executable running the tests built with cmake. Now I need to > execute it as

Re: [CMake] Establishing TDD workflow

2008-11-30 Thread Michael Jackson
I think you are looking for CTest. You build your unit test executable then have CTest run and report the results. enable_testing() add_test(ut ${EXECUTABLE_OUTPUT_PATH}/ut) then you run "make" and if that builds ok, then "make test" Mike On Nov 30, 2008, at 6:38 AM, Slava Tutushkin wrote:

[CMake] Establishing TDD workflow

2008-11-30 Thread Slava Tutushkin
Hi all, I'm only starting with cmake, so my question can be quite lame. However, I have read the "Mastering Cmake" and googled a lot about it already. I have executable running the tests built with cmake. Now I need to execute it as a part of build process. I'm building the exec with the followi