[CMake] Problem on an "external" library depending on an "internal" one

instruct cmake to write the targets so that the dependencies chain is preserved and if an external depends on an internal, the internal is built before the link stage? Thanks in advance. Marco -- Marco Corvo SuperB Experiment CNRS - Orsay c/o INFN Padova -- Powered by www.kitware.com Visit o

Re: [CMake] Again on dependencies tree

Hi Michael, thanks for the hints. It works! Cheers, Marco On 9/26/11 8:00 PM, Michael Hertling wrote: On 09/22/2011 01:00 PM, Marco Corvo wrote: Hi all, I thought I came up with a solution for this problem, but looks like I'm still not doing the right thing. My project is made of

[CMake] Again on dependencies tree

directories, and find_package, but it would be rather complicated in case my libA.a depends on N other libraries. Am I missing any CMake instructions? Or is it simply the wrong way to proceed? Sorry for the long mail and thanks in advance. Cheers, Marco -- Marco

[CMake] Bug in cmake 2.8.4/5 when using IMPORTED static targets?

pointer and when IsImported() is called on it, it makes the program crash. Have anyone else tried to use this feature of cmake 2.8.4 and eventually discovered this issue? Cheers, Marco -- Marco Corvo SuperB experiment CNRS - Orsay c/o INFN - Padova __

[CMake] Build the dependencies tree of an executable

on some libs and indirectly on some other ones? Consider that I build static libraries, so I need to have the full list of libraries when linking the executable. Thanks in advance for your help. Cheers Marco -- Marco Corvo SuperB experiment CNRS - Orsay c/o INFN - Padova ___