Re: [CMake] Dependencies between independent projects

Hi Peter, Thanks for your reply, 2012/4/30 Petr Kmoch > Hi Alexander, > > I had to create a very similar setup at work. My solution was to > define a global property for the list of projects to generate. There > is a top level CMakeLists.txt file which doesn't define any targets, > but just inc

Re: [CMake] Dependencies between independent projects

Hi, I'm very interested in this solution and the results if it is finished. Could you keep me up to date if you have something working? Thx! 2012/4/30 Arnault Christian > Hi > > We have been using a configuration system named CMT which exactly cope > with this issue > It used to be directly b

Re: [CMake] Dependencies between independent projects

I've run into this issue before and posted a question about this on Programmers.StackExchange[1]. While the exact workflow I present is for Git & CMake, the question is really similar. The idea is to have a certain library B that depends on library A, as well as a program C that depends on B and

Re: [CMake] Using CMake with ifort compiler

On 5/2/12 11:38 AM, Vivek Venugopal wrote: CMAKE_FORTRAN_LINK_EXECUTABLE variable missing I don't see any add_executable() or add_library(). I don't know that either is required, but I wonder how CMake is to figure out what it needs to build. -- Powered by www.kitware.com Visit other Kitware

[CMake] Running Python unit tests importing modules built in CMake

I'm building Python modules using SWIG and CMake, and have run into a problem running Python unit tests for these built modules. I can not find a slick way to set the Python module search path when running the test. The usual trick of setting sys.path in the scripts will not work here because I

[CMake] ctest and gcov and cdash

Hi, I can't find any documentation that describes gcov integration with ctest in depth, though there seems to be a fair amount of integration with it, as well as with cdash. As far as I can tell, you're supposed to compile with -fprofile-arcs -ftest-coverage -lgcov and then run all your tests

[CMake] Why does CMAKE_FIND_FRAMEWORK always default to FIRST ignoring command line definitions?

This is observed OS X 10.6.8, XCode 4.2.6 and 10.7.3, XCode 4.3 with CMake 2.8.8. Say I have the following CMakeLists.txt: PROJECT(find_tst) CMAKE_MINIMUM_REQUIRED(VERSION 2.8.8) MESSAGE(STATUS "Value of CMAKE_FIND_FRAMEWORK: ${CMAKE_FIND_FRAMEWORK}") Why does CMAKE_FIND_FRAMEWORK e

Re: [CMake] ctest and gcov and cdash

Apologies. In checking again, these flags were not being passed during the compile phase. I'll go fix that and bump this if it still doesn't work. Sent from my iPhone On May 2, 2012, at 17:32, Leif Walsh wrote: > Hi, > > I can't find any documentation that describes gcov integration with cte

Re: [CMake] Eclipse project and MKL libraries

Hi Eric,Thank you, it is solved now. I got working Eclipse project in Mac OS X and Ubuntu 12.04.On Apr 30, 2012, at 3:30 PM, Eric Noulard wrote:Did you try starting eclipse from the same command line (in order tomake eclipse inherit the environment setup you have in that commandline) and compiling

Re: [CMake] Running Python unit tests importing modules built in CMake

Are you using "add_test" to add the tests in the CMakeLists file? If so, you can set the test ENVIRONMENT property to set PYTHONPATH when ctest executes the test. See property doc here: http://cmake.org/cmake/help/v2.8.8/cmake.html#prop_test:ENVIRONMENT On Wed, May 2, 2012 at 5:17 PM, Lori A.

Re: [CMake] Eclipse project and MKL libraries

2012/5/3 Giovanni Azua : > Hi Eric, > > Thank you, it is solved now. I got working Eclipse project in Mac OS X and > Ubuntu 12.04. > > On Apr 30, 2012, at 3:30 PM, Eric Noulard wrote: > > Did you try starting eclipse from the same command line (in order to > make eclipse inherit the environment set