Re: [CMake] How to handle a submodule existing twice in a project?

> > Yeah. Well, in that case I'd simply check for the TestB target thats > defined in TestB/CMakeLists.txt as condition for the top-levels > add_subdirectory: > > if(NOT TARGET TestB) > add_subdirectory(TestB) > endif() > > That should work. > > Andreas > Awesome, that seems to do the trick. Tha

Re: [CMake] How to handle a submodule existing twice in a project?

Hi, On Thu, May 17, 2012 at 11:36 PM, David Doria wrote: > Why are you doing that? If TestB is always available as sub-dir under >> TestA it doesn't make much sense to also add it as a subdirectory of the >> parent of TestA - IMHO. Test/CMakeLists.txt can still use all targets from >> TestB, sin

[CMake] Fwd: Build shared and static in one build

-- Forwarded message -- From: Eric Noulard Date: 2012/5/18 Subject: Re: [CMake] Build shared and static in one build To: to...@dunescientific.com 2012/5/18 Totte Karlsson : > Hi, > > How does one gey a setup where both a static and shared version of a library > is built in 'one g

Re: [CMake] install command installing symbolic links rather than files

2012/5/17 EXT-York, Gantry : > In our build tree, we have symbolic links to COTS libraries located > elsewhere.  When we do the install, it copies these symbolic links into the > run tree when we would actually like a copy of the source of these links > (the file) in the run tree. What is "the run

[CMake] Build shared and static in one build

Hi, How does one gey a setup where both a static and shared version of a library is built in 'one go' in CMake? Is that possible? -totte -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-to

Re: [CMake] How to handle a submodule existing twice in a project?

> > Why are you doing that? If TestB is always available as sub-dir under > TestA it doesn't make much sense to also add it as a subdirectory of the > parent of TestA - IMHO. Test/CMakeLists.txt can still use all targets from > TestB, since target names are always valid across the complete project.

Re: [CMake] How to handle a submodule existing twice in a project?

Hi, On Thu, May 17, 2012 at 11:20 PM, David Doria wrote: > I have a main project (called Test) that has two submodules, TestA and > TestB. TestA also has a submodule, which is exactly the same TestB. > > So there is a directory Test/TestB as well as Test/TestA/TestB > > In TestA/CMakeLists.txt,

Re: [CMake] Linking to libraries that depend on other libraries

Hi, On Thu, May 17, 2012 at 10:50 PM, David Doria wrote: > On Thu, May 17, 2012 at 2:18 AM, Petr Kmoch wrote: > >> Hi David, >> >> there's a target property LINK_INTERFACE_LIBRARIES (and >> per-configuration variants) which can be used for this purpose. >> Starting with 2.8.7, target_link_libra

[CMake] How to handle a submodule existing twice in a project?

I have a main project (called Test) that has two submodules, TestA and TestB. TestA also has a submodule, which is exactly the same TestB. So there is a directory Test/TestB as well as Test/TestA/TestB In TestA/CMakeLists.txt, I have add_subdirectory(TestB). In Test/CMakeLists.txt, I have add_sub

[CMake] install command installing symbolic links rather than files

In our build tree, we have symbolic links to COTS libraries located elsewhere. When we do the install, it copies these symbolic links into the run tree when we would actually like a copy of the source of these links (the file) in the run tree. Is there a way to make the install command copy th

Re: [CMake] Linking to libraries that depend on other libraries

On Thu, May 17, 2012 at 2:18 AM, Petr Kmoch wrote: > Hi David, > > there's a target property LINK_INTERFACE_LIBRARIES (and > per-configuration variants) which can be used for this purpose. > Starting with 2.8.7, target_link_libraries() also accepts > LINK_INTERFACE_LIBRARIES as a new argument mod

Re: [CMake] Secret precompiled header support?

Hey Bill, First of all apologies if I have offended anyone, my goal wasn't to disrespect CMake or anyone's efforts they put into it. Perhaps I made a poor choice of words. What I was trying to convey with my use of the word "professional" was to say that there are areas that seem inconsistent or

Re: [CMake] target_link_libraries chain dynamic->static

Hi Anton, you should look into target property LINK_INTERFACE_LIBRARIES (and its per-configuration variants) which controls "transitive linking." target_link_libraries() also accepts LINK_INTERFACE_LIBRARIES as an argument mode, which sets the property instead of linking. Petr On Thu, May 17, 20

[CMake] target_link_libraries chain dynamic->static

Hello! I use 2.8.8 and my build chais is following: I have 3 static libs - A.a, B.a, C.a. I'm creating new D.so (add_library .. SHARED .. ) with limited set on functions from static libs (linking -lA -lB -lC to resolve functions). Then I'm creating application, wich use D.so as main library. I'm

Re: [CMake] copy dependant shared libs locally

Hi Daniel. In general, that is not possible with cmake at the moment. What I currently do is have two custom targets, one for copying to debug, one for copying to release. It's annoying that both get run in either configuration, but I couldn't find a better way around it. There are some bugreport

Re: [CMake] Linking to libraries that depend on other libraries

Hi Am Donnerstag, 17. Mai 2012 schrieb Petr Kmoch : > Hi David, > > there's a target property LINK_INTERFACE_LIBRARIES (and > per-configuration variants) which can be used for this purpose. > Starting with 2.8.7, target_link_libraries() also accepts > LINK_INTERFACE_LIBRARIES as a new argument mo

[CMake] copy dependant shared libs locally

Hello, I would like to trace shared library dependencies between targets (and also to external packages) and then copy required dll's to output bin directory (so that they are immediately available, without PATH editing) in the post-build. However, for debug configuration, I need to copy debug dll