Re: [cmake-developers] Ninja: Recognize OBJECT and CMAKE_C_COMPILER in CMAKE_DEPFILE_FLAGS_${lang}

2012-03-23 Thread Brad King
On 3/22/2012 12:23 PM, Amine Khaldi wrote: I've attached a patch that allows us (ReactOS) ... to properly track dependencies in rc files. Peter, as maintainer of the Ninja generator how does this look to you? Thanks, -Brad -- Powered by www.kitware.com Visit other Kitware open-source

[cmake-developers] When should a library be in LINK_INTERFACE_LIBRARIES?

2012-03-23 Thread Stephen Kelly
Hi there, I'm trying to get the IMPORTED_LINK_INTERFACE_LIBRARIES for Qt modules correct. There is a debate over the QtQml module at the moment. It has in one of its interface classes (QQmlEngine) a method QNetworkAccessManager *networkAccessManager() const, and the QNetworkAccessManager

Re: [cmake-developers] When should a library be in LINK_INTERFACE_LIBRARIES?

2012-03-23 Thread Brad King
On 3/23/2012 9:15 AM, Stephen Kelly wrote: There is a debate over the QtQml module at the moment. It has in one of its interface classes (QQmlEngine) a method QNetworkAccessManager *networkAccessManager() const, and the QNetworkAccessManager class is forward declared.

[cmake-developers] [CMake 0013060]: FindQt4 relies on the command 'qmake -query QT_INSTALL_LIBS' to determine the lib path and ignores FIND_LIBRARY_USE_LIB64_PATHS

2012-03-23 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=13060 == Reported By:Claus Christmann Assigned To:

Re: [cmake-developers] CMake 2.8.8-rc1 ready for testing!

2012-03-23 Thread Alexander Neundorf
On Friday 23 March 2012, David Cole wrote: I am happy to announce that CMake 2.8.8 has entered the release candidate stage! You can find the source and binaries here: http://www.cmake.org/files/v2.8/?C=M;O=D This email is also available on the Kitware blog:

Re: [cmake-developers] CMake 2.8.8-rc1 ready for testing!

2012-03-23 Thread David Cole
Nice summary of the changes :-) Danka! -- 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

Re: [cmake-developers] CMake 2.8.8-rc1 ready for testing!

2012-03-23 Thread Alexander Neundorf
On Friday 23 March 2012, David Cole wrote: Nice summary of the changes :-) Danka! In German this would be Danke ;-) Alex -- 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

Re: [cmake-developers] CMake 2.8.8-rc1 ready for testing!

2012-03-23 Thread David Cole
On Fri, Mar 23, 2012 at 3:43 PM, Alexander Neundorf neund...@kde.org wrote: On Friday 23 March 2012, David Cole wrote: Nice summary of the changes :-) Danka! In German this would be Danke ;-) Alex Dang! How do say sorry ...? ;-P -- Powered by www.kitware.com Visit other Kitware

Re: [CMake] Different targets for different configurations

2012-03-23 Thread Eric Noulard
2012/3/23 Mike Krus m...@mve.com: Hi I would like run a script with different options for debug and release builds. I can do this easily for Makefiles but am struggling to get it to work for Visual Studio. I basically: - add a custom command the output of which depends on the configuration

Re: [CMake] Different targets for different configurations

2012-03-23 Thread Mike Krus
On 23/03/2012 06:53, Eric Noulard wrote: Why can't you use the PRE_BUILD options of add_custom_command with TARGET target signature? It is not possible because this script should be run before any target? I was looking at using targets do make sure the script only once and did so before any

Re: [CMake] Different targets for different configurations

2012-03-23 Thread Mike Krus
On 23/03/2012 09:10, Mike Krus wrote: Technically, that command could run when CMake is invoked (ie before any build invocation). In that case, if the generator is Visual Studio, I would simple run the script twice, once with parameters compatible for debug, once for release... Is there a way to

Re: [CMake] Different targets for different configurations

2012-03-23 Thread Petr Kmoch
Also, this: http://public.kitware.com/Bug/view.php?id=12877 and especially this: http://public.kitware.com/Bug/view.php?id=9974 The latter one even has a patch attached - maybe it could be merged? On Fri, Mar 23, 2012 at 10:33 AM, Mike Krus m...@mve.com wrote: On 23/03/2012 09:10, Mike Krus

[CMake] Dependencies between libraries

2012-03-23 Thread Peter Eastman
My project involves a set of plugin libraries. Those libraries get loaded dynamically at runtime, e.g. by calling dlopen(). The user can install them to any location they want, so the directory won't necessarily be in the library path. I can safely assume, though, that they'll all be in the

[CMake] make install/strip does not strip static libraries

2012-03-23 Thread Kyle Leber
Hi, I'm using cmake 2.8 and having an issue when I issue a 'make install/strip'. My project includes two libraries: one static and one shared. The shared library gets properly stripped, but the static one does not. Do I need to specify a special parameter to get the static library to be

[Cmake-commits] CMake branch, master, updated. v2.8.7-793-g9d6b7be

2012-03-23 Thread Brad King
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, master has been updated via 9d6b7bed7abdc0debde6476c8c2b0935bf5015f0 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.7-3338-g9520737

2012-03-23 Thread Brad King
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 9520737f02106dc9581df439a5b33d7ae009bf8b (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.7-794-gc160f63

2012-03-23 Thread KWSys Robot
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, master has been updated via c160f63490e9aab588cc04a62fac81cf774e4f92 (commit) from