Re: [cmake-developers] Adding the OpenRAVE library module

set_property(TARGET mysharedlib PROPERTY LINK_INTERFACE_LIBRARIES ) but wouldn't that also affect how the libraries are linked? for example, libopenrave target links to boost. and any module using libopenrave should still use boost. however the static libraries libopenrave links to like crlibm

Re: [cmake-developers] Adding the OpenRAVE library module

After thinking about it, it really doesn't make sense for static libraries to be part of the exports. rosen, 2011/4/15 Rosen Diankov rosen.dian...@gmail.com:  set_property(TARGET mysharedlib PROPERTY LINK_INTERFACE_LIBRARIES ) but wouldn't that also affect how the libraries are linked? for

[cmake-developers] [CMake 0012093]: Add brief configuration instructions in output

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12093 == Reported By:David Doria Assigned To:

Re: [cmake-developers] Adding the OpenRAVE library module

On 04/15/2011 09:48 AM, Rosen Diankov wrote: From what i understood in the documentation, I would have to set LINK_INTERFACE_LIBRARIES to all the non-static install libraries right? Yes. It should list the libraries that applications should link when linking to your library. If your public

[cmake-developers] [CMake 0012095]: DetermineVSServicePack() does not properly sense service pack for vc100

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12095 == Reported By:Doug Barbieri Assigned To:

[CMake] RPATH on Mac

Dear all I have a project in which I would like to use rpath on Mac OS. Everything is going fine if I am building everything manually (i.e. without CMake) With CMake all is fine for the libs between the build and the installation, all libs are processed with install_name_tool. But nothing is

Re: [CMake] CDash Dynamic Analysis

Hi This doesn't seem to be very easy, fun or well documented. I'v resolved to looking aroung the CTest source code to see what is going on. From what I'v found out, there seems to be some syntax to what the defect list contains! DefectList Defect Type=mystery/ DefectList I'm not

[CMake] Extended path for imported .proto files in the FindProtobuf module

Hi, The current implementation (as of 2.3.8) of the FindProtobuf module implicitly assumes that the imported .proto files are located only in the ${CMAKE_CURRENT_SOURCE_DIR}. This may not be true for more complex source directory structure. The attached patch allows users to override the

[CMake] Post-Build commands on custom targets are always executed?

Hi, I observe that a custom command attached to a custom target as POST-BUILD is launched on every build. Is that true? or is it a misconfiguration on my side? Bye, Oliver ___ Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [CMake] Post-Build commands on custom targets are always executed?

On 04/15/2011 11:22 PM, Oliver Buchtala wrote: Hi, I observe that a custom command attached to a custom target as POST-BUILD is launched on every build. Is that true? or is it a misconfiguration on my side? Bye, Oliver A custom target is always out of date, i.e. it is always rebuilt

Re: [CMake] Post-Build commands on custom targets are always executed?

Am 15.04.2011 23:48, schrieb Michael Hertling: On 04/15/2011 11:22 PM, Oliver Buchtala wrote: Hi, I observe that a custom command attached to a custom target as POST-BUILD is launched on every build. Is that true? or is it a misconfiguration on my side? Bye, Oliver A custom target is

[CMake] rebuild

I have a visual studio 2010 solution that I create with cmake. I have about 10 projects in the solution. Nine of these are open source libraries im using. The 10th is obviously the project I am currently working on. When I do a rebuild, it takes several minutes because it recompiles all the 3rd

[Cmake-commits] CMake branch, next, updated. v2.8.4-1445-g4af24ea

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 4af24ea7936ec791dbe374c83ff1e6c5ad93028b (commit) via