Re: [CMake] CMakeEd Eclipse Plugin has another Release Candidate Ready.

On Nov 30, 2008, at 3:10 PM, Eric Noulard wrote: 2008/11/30 Michael Jackson <[EMAIL PROTECTED]>: I have posted another Release Candidate for the CMakeEd Eclipse Plugin. You can download it from . Fixed in this release is better indexing of user defined variab

Re: [CMake] Invoking "make" with CMake scripts?

On Sat, Nov 29, 2008 at 3:52 PM, Mike Arthur <[EMAIL PROTECTED]> wrote: > > The typical way this is handled in both CMake and generally is that you > rely > on the builder of your sourcecode to have the dependencies already > installed > and then use Find* modules to determine if the libraries are

Re: [CMake] CMakeEd Eclipse Plugin has another Release Candidate Ready.

2008/11/30 Michael Jackson <[EMAIL PROTECTED]>: > I have posted another Release Candidate for the CMakeEd Eclipse Plugin. You > can download it from . > > Fixed in this release is better indexing of user defined variables and > updated documentation generated from CM

[CMake] CMakeEd Eclipse Plugin has another Release Candidate Ready.

I have posted another Release Candidate for the CMakeEd Eclipse Plugin. You can download it from . Fixed in this release is better indexing of user defined variables and updated documentation generated from CMake itself. I also added the ability to open any c

Re: [CMake] Adding ext. libs only to one target and not transitively to others

Am Saturday 29 November 2008 00:13:26 schrieb Klaus Drechsler: > How can I prevent cmake from adding 'myextlib' to any other targets? I > only want it to be added to 'func1' nowhere else. > > Or, if this is not possible, how can I propagate the link directory and > include directory 'up' to the tar

Re: [CMake] Establishing TDD workflow

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

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

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

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