http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42280 <pre> Awesome, that seems to do the trick. Thanks! David -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> David Doria 2012-05-17T23:15:43 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42279 <pre>Hi, On Thu, May 17, 2012 at 11:36 PM, David Doria &lt;daviddoria-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote: 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 -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Andreas Pakulat 2012-05-17T23:01:00 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42278 <pre>---------- Forwarded message ---------- From: Eric Noulard &lt;eric.noulard-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; Date: 2012/5/18 Subject: Re: [CMake] Build shared and static in one build To: totte-A63wRcIvbn5zKiIawvo0wdBPR1lH4CV8&lt; at &gt;public.gmane.org 2012/5/18 Totte Karlsson &lt;totte-A63wRcIvbn5zKiIawvo0wdBPR1lH4CV8&lt; at &gt;public.gmane.org&gt;: set(LIBSRC blah.c bouh.c) add_library(MyLib SHARED ${LIBSRC}) add_library(MyLib-static STATIC ${LIBSRC}) set_target_properties(MyLibStatic PROPERTIES OUTPUT_NAME MyLib) should work -- Erk Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org </pre> Eric Noulard 2012-05-17T22:29:16 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42277 <pre>2012/5/17 EXT-York, Gantry &lt;gantry.york-X8CqP27nNzzQT0dZR+AlfA&lt; at &gt;public.gmane.org&gt;: What is "the run tree"? The tree resulting from installation? I don't think that having a symlink to external in build tree is a good practice, why are you doing that? May be you could 1) configure_file(.... COPYONLY) the COTS lib instead of symlink or 2) use an IMPORTED library using: add_library(&lt;name&gt; &lt;SHARED|STATIC|MODULE|UNKNOWN&gt; IMPORTED) set_property(TARGET &lt;name&gt; PROPERTY IMPORTED_LOCATION /path/to/name) cmake --help-command add_library http://www.cmake.org/Wiki/CMake/Tutorials/Exporting_and_Importing_Targets I don't think so, if you want that I think you should copy the target at CMake time as in suggested in method 1). If you want to "bundle" those external libs with your software, may be you should have a look at BundleUtilities.cmake cmake --help-module BundleUtilities </pre> Eric Noulard 2012-05-17T22:18:52 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42276 <pre>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-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake </pre> Totte Karlsson 2012-05-17T22:14:46 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42275 <pre> I use functionality of TestB in Test. If TestA decides to remove TestB, then Test will break. I was trying to "hide" the implementation of TestA by requiring both TestA and TestB to be submodules of Test, regardless of whether or not TestA has TestB as a submodule of its own. See what I mean? David -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> David Doria 2012-05-17T21:36:24 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42274 <pre>Hi, On Thu, May 17, 2012 at 11:20 PM, David Doria &lt;daviddoria-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; 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, since target names are always valid across the complete project. Since TestA is a submodule, it should always be present in the sources anyway. Andreas -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Andreas Pakulat 2012-05-17T21:31:55 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42273 <pre>Hi, On Thu, May 17, 2012 at 10:50 PM, David Doria &lt;daviddoria-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote: You forgot to link TestA to TestB here, I guess your c++ code currently does not actually expose any dependency? Thats why cmake doesn't include TestB when linking the executable. The LINK_INTERFACES_LIBRARIES only helps cmake to decide when a particular library doesn't need to be added to the linker-command for the executable. By default cmake will link the executable against the libraries specified by you and any libraries these link to - recursively. The property just allows to disable this behaviour by defining which dependent libraries a given library exposes in its public API and hence which dependent libraries an executable might need to link against in addition to the main library. Andreas -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.</pre> Andreas Pakulat 2012-05-17T21:28:42 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42272 <pre>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_subdirectory(TestA) as well as add_subdirectory(TestB). CMake complains that it cannot create TestB because another target with the same name already exists (which it does). What is the right way to handle this? I always assume that TestB is identical in both places (which might not be a great assumption...), so I guess I just want, in both places, to say "include TestB if it already hasn't been included." I tried to do that by replacing the add_subdirectory(TestB) calls with: if(NOT TestB_SOURCE_DIR) add_subdirectory(TestB) endif() but then the linker complains that it can't find TestB. I have uploaded a demo project here: http://homepages.rpi.edu/~doriad/Upload/TestCMake2.tar.gz Thanks! David -- Powered by w</pre> David Doria 2012-05-17T21:20:16 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42271 <pre>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 the file that is the source of the symbolic link rather than the symbolic link itself? Gantry York Boeing/KinetX Iridium SCS Development Team -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> EXT-York, Gantry 2012-05-17T20:56:05 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42270 <pre> Petr, I tried the following, but in both cases (target_link_libraries and set_target_properties) I still get a linker error that it can't find TestB(). cmake_minimum_required(VERSION 2.6) PROJECT(Test) add_library(TestB TestB.cpp) # TestA depends on TestB add_library(TestA TestA.cpp) #target_link_libraries(TestA LINK_INTERFACE_LIBRARIES TestB) set_target_properties(TestA PROPERTIES LINK_INTERFACE_LIBRARIES "TestB") # I want to link to TestA and have it automatically also link to TestB add_executable(Test Test.cpp) target_link_libraries(Test TestA) I have uploaded the entire demo project here: http://homepages.rpi.edu/~doriad/Upload/TestCMake.tar.gz Any ideas? Thanks, David -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> David Doria 2012-05-17T20:50:48 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42269 <pre>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 odd to use, and by making those more consistent it seems more professional. Perhaps instead of saying professional, I should just say consistent :) Normally when you encounter "professional" software (that is, software that you pay for, that is generally well designed and maintained by a single entity), it has a consistent feel. Open source naturally can feel inconsistent because of the large number of contributions, which sometimes don't follow the same implementation patterns. I hope that clarifies what I meant. An example, as I had stated, is general compiler flag support. For example, we have convenience methods for includes and preprocessor definitions, but PCH and warning levels does not have such a thing. O</pre> Robert Dailey 2012-05-17T16:50:58 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42268 <pre>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, 2012 at 3:07 PM, Anton Sibilev &lt;anton.sibilev-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote: -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake </pre> Petr Kmoch 2012-05-17T14:21:57 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42267 <pre>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 linking it with target_link_libraries(target D.so). But finally, my link cmdline is following: -o application -lD -lA -lB -C. But I want to link only one shared lib - D.so! As I understand this is results of caching libs. How I can resolve this? Thanks! -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Anton Sibilev 2012-05-17T13:07:31 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42266 <pre>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 bugreports in cmake's tracker, you might find some inspiration there: http://public.kitware.com/Bug/view.php?id=9974 http://public.kitware.com/Bug/view.php?id=12877 Petr On Thu, May 17, 2012 at 9:12 AM, Daniel Krikun &lt;krikun.daniel-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote: -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake </pre> Petr Kmoch 2012-05-17T07:43:35 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42265 <pre>Hi Am Donnerstag, 17. Mai 2012 schrieb Petr Kmoch : Actually using link_interface_libraries in target_link_libraries works already in 2.6.4 I believe, since KDE uses that and requires that cmake version at the moment. Andreas -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Andreas Pakulat 2012-05-17T07:27:44 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42264 <pre>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's (usually with 'd' suffix) and for release configuration - release dll's. I can copy files to run-time directory using add_custom_command, but how could I make a distinction for the release-debug files? Thanks, </pre> Daniel Krikun 2012-05-17T07:12:51 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42263 <pre>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 mode, setting the property instead of linking. Petr On Wed, May 16, 2012 at 11:19 PM, David Doria &lt;daviddoria-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote: -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake </pre> Petr Kmoch 2012-05-17T06:18:10 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42262 <pre>Thanks very much for the feedback. I will look into the module stuff, where the compiler puts it etc. Petr On Wed, May 16, 2012 at 10:24 PM, Brad King &lt;brad.king-5opLkZggLXlBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; wrote: -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake </pre> Petr Kmoch 2012-05-17T06:15:35 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42261 <pre>Using the keyword SHARED in the add_library command will always build a shared library regardless of the BUILD_SHARED_LIBS value. On May 16, 2012, at 6:15 PM, Totte Karlsson &lt;totte-A63wRcIvbn5zKiIawvo0wdBPR1lH4CV8&lt; at &gt;public.gmane.org&gt; wrote: -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake </pre> David Cole 2012-05-17T02:30:38 http://permalink.gmane.org/gmane.comp.programming.tools.cmake.user/42260 <pre>So, I do take offense to this language. Kitware does take CMake seriously and we are always "moving" to make it better. However, since it is an open source project, we do not get any direct revenue from CMake. We do of course receive revenue from companies and agencies willing to hire us to implement features or develop CMake build systems for them. If your company wants generic pre-compiled header support, we would love for you to hire Kitware to implement it. If you are working on an open source project and you would like to contribute pch support that would be great as well. I think the fact that you are able to do what you need to do, even with a bit of extra work speaks to the "professionalism" and flexibility of CMake. If you were unable to create a working build system that supported PCH and the other features you found missing in CMake, that would be a failure of CMake. If at the moment CMake does not have an elegant way to achieve a particular goal, I don't think that makes it an</pre> Bill Hoffman 2012-05-17T01:47:54 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.programming.tools.cmake.user