Re: [cmake-developers] Interface includes and defines plumbing

2013-01-07 Thread Brad King
On 01/04/2013 12:09 PM, Stephen Kelly wrote: Brad King wrote: Yes, please. Thanks for splitting this out. Done, thanks, Thanks for cleaning up the dashboard trouble. I've merged this to master! -Brad -- Powered by www.kitware.com Visit other Kitware open-source projects at

[cmake-developers] LINK_LIBRARIES property topic

2013-01-07 Thread Brad King
Steve, I've reviewed this topic: 4cf80cc Make sure types match exacty without conversion when making std::pairs. 786aa36 Fix (hopefully) the Mac build. 9bb1f54 Populate the LINK_LIBRARIES property when linking to targets. 1381d56 Add a HEAD-target to target linking API. I'm hesitant to use

Re: [cmake-developers] Interface includes and defines plumbing

2013-01-07 Thread Stephen Kelly
Brad King wrote: On 01/04/2013 12:09 PM, Stephen Kelly wrote: Brad King wrote: Yes, please. Thanks for splitting this out. Done, thanks, Thanks for cleaning up the dashboard trouble. I've merged this to master! Great, thanks! I've pushed two new branches to my gitorious clone.

Re: [cmake-developers] LINK_LIBRARIES property topic

2013-01-07 Thread Stephen Kelly
Brad King wrote: Steve, I've reviewed this topic: 4cf80cc Make sure types match exacty without conversion when making std::pairs. 786aa36 Fix (hopefully) the Mac build. 9bb1f54 Populate the LINK_LIBRARIES property when linking to targets. 1381d56 Add a HEAD-target to target linking

Re: [cmake-developers] Interface includes and defines plumbing

2013-01-07 Thread Stephen Kelly
Brad King wrote: On 01/07/2013 02:50 PM, Stephen Kelly wrote: I've pushed two new branches to my gitorious clone. include-dirs-convenience For the same reason that CMAKE_INCLUDE_CURRENT_DIR exists, but for interfaces. Please let me know what you think about the idea and API. The

Re: [cmake-developers] Interface includes and defines plumbing

2013-01-07 Thread Brad King
On 01/07/2013 03:36 PM, Stephen Kelly wrote: Perhaps it should be install(TARGETS testLibRequired EXPORT RequiredExp DESTINATION lib INTERFACE_INCLUDES /foo/bar ) ? That looks better, but I think it is best to wait until we gain more experience with the

Re: [cmake-developers] Review request: Qt4 interface includes and defines (Was Re: Interface includes and defines plumbing)

2013-01-07 Thread Clinton Stimpson
On Monday, January 07, 2013 08:55:40 PM Stephen Kelly wrote: Stephen Kelly wrote: Brad King wrote: On 01/04/2013 12:09 PM, Stephen Kelly wrote: Brad King wrote: Yes, please. Thanks for splitting this out. Done, thanks, Thanks for cleaning up the dashboard trouble. I've merged

Re: [cmake-developers] LINK_LIBRARIES property topic

2013-01-07 Thread Brad King
On 01/07/2013 03:26 PM, Stephen Kelly wrote: Brad King wrote: Also, I see a few uses of GetOriginalLinkLibraries left. The only one we should have left is the one for the CMP0003 OLD behavior. The other uses are in cmGlobalGenerator and in the Graphiviz generator. In cmGlobalGenerator it

Re: [cmake-developers] Review request: Qt4 interface includes and defines

2013-01-07 Thread Stephen Kelly
Clinton Stimpson wrote: On Monday, January 07, 2013 08:55:40 PM Stephen Kelly wrote: Stephen Kelly wrote: Brad King wrote: On 01/04/2013 12:09 PM, Stephen Kelly wrote: Brad King wrote: Yes, please. Thanks for splitting this out. Done, thanks, Thanks for cleaning up the

Re: [cmake-developers] Interface includes and defines plumbing

2013-01-07 Thread Stephen Kelly
Brad King wrote: On 01/07/2013 03:36 PM, Stephen Kelly wrote: Perhaps it should be install(TARGETS testLibRequired EXPORT RequiredExp DESTINATION lib INTERFACE_INCLUDES /foo/bar ) ? That looks better, but I think it is best to wait until we gain more

Re: [cmake-developers] Request for Comments: Will implementing an interactive CMake debugger be welcome?

2013-01-07 Thread Matt McCormick
Hi Shlomi, I also think this would be a great feature. I started on an implementation here: https://github.com/thewtex/cmakedbg but I have not had time to follow it through. The user interface is written in Python/Cython for fast prototyping purposes, but it could be written all C/C++ if

[cmake-developers] DESTDIR does not work correctly with install(FILES ... signature

2013-01-07 Thread Alan W. Irwin
Here is a simple project to show the issue summarized in the subject line for the default Unix Makefiles generator on Linux. # Test DESTDIR cmake_minimum_required (VERSION 2.8.5) project (test_destdir NONE) INSTALL(CODE FILE(MAKE_DIRECTORY $ENV{DESTDIR}/whatever) ) This does not work

Re: [CMake] Cmake absolute paths with gcc, __FILE__ , and logging

2013-01-07 Thread Willy Lambert
2013/1/4 Gregor Jasny gja...@googlemail.com: Hello Willy, On 1/4/13 4:58 PM, Willy Lambert wrote: I am trying to convert an existing project from Manual Makefiles to Cmake for building it. We have a logger that rely on the __FILE__ define to say which file is writing into the log but this

Re: [CMake] Cmake absolute paths with gcc, __FILE__ , and logging

2013-01-07 Thread Willy Lambert
2013/1/7 Willy Lambert lambert.wi...@gmail.com: 2013/1/4 Gregor Jasny gja...@googlemail.com: Hello Willy, On 1/4/13 4:58 PM, Willy Lambert wrote: I am trying to convert an existing project from Manual Makefiles to Cmake for building it. We have a logger that rely on the __FILE__ define to

[CMake] Selective build and install of subfolders

2013-01-07 Thread screamingfist
Hello list, I have a project with subfolders that should be selectively built and installed. The problem ist that there are various dependencies between them. At the moment I have a list-variable that contains the targets I want to be built and the folders are included depending on this list:

Re: [CMake] Cmake absolute paths with gcc, __FILE__ , and logging

2013-01-07 Thread Willy Lambert
2013/1/4 Andreas Mohr a...@lisas.de: Hi, On Fri, Jan 04, 2013 at 11:47:40AM -0500, cmake-requ...@cmake.org wrote: Date: Fri, 4 Jan 2013 16:58:05 +0100 From: Willy Lambert lambert.wi...@gmail.com Hi all, Short Story : I am trying to convert an existing project from Manual Makefiles to

Re: [CMake] Cmake absolute paths with gcc, __FILE__ , and logging

2013-01-07 Thread Willy Lambert
really sorry, last mail was sent too early X-( 2013/1/7 Willy Lambert lambert.wi...@gmail.com: 2013/1/4 Andreas Mohr a...@lisas.de: Hi, On Fri, Jan 04, 2013 at 11:47:40AM -0500, cmake-requ...@cmake.org wrote: Date: Fri, 4 Jan 2013 16:58:05 +0100 From: Willy Lambert lambert.wi...@gmail.com

[CMake] Tracker.exe response file error

2013-01-07 Thread Petr Kmoch
Hi all. On Windows, Visual Studio 2010, some machines in our company experience this error ( http://connect.microsoft.com/VisualStudio/feedback/details/540902/tracker-exe-response-file-not-found) when detecting C compiler, which makes it impossible to use CMake on them. The workaround (mentioned

Re: [CMake] What is the proper cross-platform way to link the Python library?

2013-01-07 Thread Stephen Kelly
Alan W. Irwin wrote: If/when that python.org bug is fixed I will look into the Is it reported? If not it won't get fixed. I assume you saw this? http://thread.gmane.org/gmane.comp.science.paraview.user/10956/focus=11019 I wonder if that David reported it either. Thanks, Steve. --

Re: [CMake] Selective build and install of subfolders

2013-01-07 Thread Amine Chadly
screamingfist@... writes: Hello list, I have a project with subfolders that should be selectively built and installed. The problem is that there are various dependencies between them. [snip] Hi Stefan, I think you should look into options, and the CMake dependent option macro.

Re: [CMake] Ninja and *.i targets

2013-01-07 Thread Bill Hoffman
On 1/5/2013 3:49 PM, Óscar Fuentes wrote: With the `Unix Makefiles' generator, a foo.i target is generated for foo.cpp. That's very convenient. However, ninja doesn't list such targets under `ninja help' and `ninja foo.i' complains about unknown target. Is this feature missing from the ninja

Re: [CMake] Ninja and *.i targets

2013-01-07 Thread Stephen Kelly
Bill Hoffman wrote: On 1/5/2013 3:49 PM, Óscar Fuentes wrote: With the `Unix Makefiles' generator, a foo.i target is generated for foo.cpp. That's very convenient. However, ninja doesn't list such targets under `ninja help' and `ninja foo.i' complains about unknown target. Is this feature

Re: [CMake] Ninja and *.i targets

2013-01-07 Thread Óscar Fuentes
Bill Hoffman bill.hoff...@kitware.com writes: On 1/5/2013 3:49 PM, Óscar Fuentes wrote: With the `Unix Makefiles' generator, a foo.i target is generated for foo.cpp. That's very convenient. However, ninja doesn't list such targets under `ninja help' and `ninja foo.i' complains about unknown

[CMake] install(EXPORT ...) behavior for multi-configuration generators

2013-01-07 Thread Gregoire Aujay
Hello, I am using CMake 2.8.10.2, on windows. I am trying to use install(TARGETS ) and install(EXPORT ) both with NMake makefiles and with the multi-configuration generator Visual studio. I cannot get the same behavior when I want my binaries to be installed in a subfolder that depends on the

Re: [CMake] Ninja and *.i targets

2013-01-07 Thread Óscar Fuentes
Stephen Kelly steve...@gmail.com writes: While at it, you comb this thread to see if there are other feature requests there which are not in the bug tracker: http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/3471/focus=3475 Good idea. Apart from the .i targets, the only

Re: [CMake] Ninja and *.i targets

2013-01-07 Thread Stephen Kelly
Óscar Fuentes wrote: Stephen Kelly steve...@gmail.com writes: While at it, you comb this thread to see if there are other feature requests there which are not in the bug tracker: http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/3471/focus=3475 Good idea. Apart from

Re: [CMake] Cmake issue compiling CLucene

2013-01-07 Thread Hatchi
Hello Mike I also tried from the VS command prompt but it gives the same problem with the linker it seems... -- View this message in context: http://cmake.3232098.n2.nabble.com/Cmake-issue-compiling-CLucene-tp7582775p7582803.html Sent from the CMake mailing list archive at Nabble.com. --

Re: [CMake] Cmake issue compiling CLucene

2013-01-07 Thread Bill Hoffman
On 1/7/2013 3:18 PM, Hatchi wrote: Hello Mike I also tried from the VS command prompt but it gives the same problem with the linker it seems... Does this work for you: http://stackoverflow.com/questions/12267158/failure-during-conversion-to-coff-file-invalid-or-corrupt -- Bill Hoffman

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1426-gd83569b

2013-01-07 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 d83569b74e0ea6e7bde0d417262969dd6cb5705d (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1430-gfd97a2c

2013-01-07 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 fd97a2c77eb6509f70d7b9dd37b6d1e4202a7b52 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1434-gb557ecd

2013-01-07 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 b557ecd6000ff5251f9b83f213b2633af9c24156 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1436-g427d2bd

2013-01-07 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 427d2bdab9dec5861ffbaecf94266c4374681939 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1438-g7e9d998

2013-01-07 Thread Clinton Stimpson
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 7e9d998fe3afad833d1e32d3c0c3a1bc47f086f9 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-373-g34f959e

2013-01-07 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 34f959e5b11d3acbf352f20137aa17402ceb5f8e (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-379-gb5ab3f0

2013-01-07 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 b5ab3f0707cae7affa14423012997503825a867c (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1445-gaae64e3

2013-01-07 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 aae64e3bd91d3a1760302dd6addf0088d926b04c (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-394-gc2cde7f

2013-01-07 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 c2cde7f1047b2f11e7d4a466000a20d8c42394be (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1447-ge80f247

2013-01-07 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 e80f2479d8e61372a87c70c9882d6fa4970386f6 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1452-gd491ccc

2013-01-07 Thread Stephen Kelly
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 d491ccc926f3fdaf2cef1329cc9bfc77a87568ad (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1456-gd98f561

2013-01-07 Thread Rolf Eike Beer
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 d98f561003af82e31ccae2fa324441c18b5b5c33 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1458-g6e8d3f0

2013-01-07 Thread Stephen Kelly
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 6e8d3f0bc6678e22361ab2b7a0e06b7d72ef0f19 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1460-g2c7d884

2013-01-07 Thread Stephen Kelly
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 2c7d8849db2025dfd189f16771d8c6c5ff043cfc (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1464-g7e91a0f

2013-01-07 Thread Rolf Eike Beer
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 7e91a0f4baa905b8d8c635616bb8d89d18ee23c1 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1466-g1a489e5

2013-01-07 Thread Stephen Kelly
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 1a489e5c088e31b33b506b4c941b0f45f91ef161 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-395-g97758f2

2013-01-07 Thread Kitware Robot
Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index a18fcf0..528fa13 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -2,5 +2,5 @@ set(CMake_VERSION_MAJOR 2) set(CMake_VERSION_MINOR 8) set(CMake_VERSION_PATCH 10) -set(CMake_VERSION_TWEAK 20130107