[cmake-developers] [CMake 0013178]: Segfault, always reproducible but no idea why.

2012-05-01 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=13178 == Reported By:cjd Assigned To:

Re: [cmake-developers] Target usage requirements and conventions

2012-05-01 Thread Alexander Neundorf
On Sunday 29 April 2012, Stephen Kelly wrote: Hi there, The topic of 'target usage requirements' has come up several times. It's something I'd like to work further towards in CMake 2.8.9. I have created a wiki page on the KDE wiki (there for my convenience mostly) so that we can discuss

Re: [cmake-developers] Setting the INCLUDE_DIRECTORIES property before and after a target after 9106b564

2012-05-01 Thread Brad King
On 4/30/2012 8:37 PM, Raphael Kubo da Costa wrote: add_library(foo foo.c) set_directory_properties( PROPERTIES INCLUDE_DIRECTORIES ${SOME_DIRECTORY}) [snip] Is this change of behaviour intentional? CMake 2.8.8 introduced support for per-target include directories. Prior to that

Re: [cmake-developers] Setting the INCLUDE_DIRECTORIES property before and after a target after 9106b564

2012-05-01 Thread Raphael Kubo da Costa
Brad King brad.k...@kitware.com writes: CMake 2.8.8 introduced support for per-target include directories. Prior to that the directory-level INCLUDE_DIRECTORIES property was documented as read-only: $ cmake --help-property INCLUDE_DIRECTORIES cmake version 2.8.7 INCLUDE_DIRECTORIES

[cmake-developers] Test suite broken if PackageMaker not installed in default location

2012-05-01 Thread Nicolas Desprès
Hi, On MacOXS I used to have the SimpleInstall test failing because it could not find the PackageMaker compiler. After looking into the code, I realized I had to set CPACK_INSTALLER_PROGRAM. But this variable does not get used by the test. So the only solution I had was to move PackageMaker to

Re: [cmake-developers] Test suite broken if PackageMaker not installed in default location

2012-05-01 Thread David Cole
Are you talking about PackageMaker from Xcode 4.3, which you must take extra care to install yourself (in any location you'd like...)? Or are you talking about PackageMaker from an earlier Xcode? And which version of cmake/cpack? The recent work to add support for Xcode 4.3 searches several

Re: [cmake-developers] Test suite broken if PackageMaker not installed in default location

2012-05-01 Thread Nicolas Desprès
Sorry for the lake of information. On Tue, May 1, 2012 at 4:51 PM, David Cole david.c...@kitware.com wrote: Are you talking about PackageMaker from Xcode 4.3, which you must take extra care to install yourself (in any location you'd like...)? Yes Xcode 4.3 and I have installed PackageMaker

Re: [cmake-developers] Test suite broken if PackageMaker not installed in default location

2012-05-01 Thread David Cole
2012/5/1 Nicolas Desprès nicolas.desp...@gmail.com: Sorry for the lake of information. On Tue, May 1, 2012 at 4:51 PM, David Cole david.c...@kitware.com wrote: Are you talking about PackageMaker from Xcode 4.3, which you must take extra care to install yourself (in any location you'd

Re: [cmake-developers] Test suite broken if PackageMaker not installed in default location

2012-05-01 Thread Eric Noulard
2012/5/1 David Cole david.c...@kitware.com: That's what I saw actually, but mine was not in the list. Setting CPACK_INSTALLER_PROGRAM as in line 390 does not help because the it is not transfered to the test project. Is there a robust way to tell cmake where is installed PackageMaker if it

Re: [cmake-developers] Version-specific documentation pages (was: Could a cmake_maximum_required() work?)

2012-05-01 Thread Brad King
On 4/25/2012 2:17 PM, Stephen Kelly wrote: This issue came up because KDE wants to ensure that developers do not accidentally use features of newer versions of CMake. It will be helpful to reference documentation specific to the minimum required CMake version to avoid using features from newer

Re: [cmake-developers] Target usage requirements and conventions

2012-05-01 Thread Stephen Kelly
Brad King wrote: On 4/29/2012 11:02 AM, Stephen Kelly wrote: The topic of 'target usage requirements' has come up several times. It's something I'd like to work further towards in CMake 2.8.9. I have created a wiki page on the KDE wiki (there for my convenience mostly) so that we can

Re: [cmake-developers] Target usage requirements and conventions

2012-05-01 Thread Stephen Kelly
Stephen Kelly wrote: This avoids the 'double booking' problem[1], which I think might be real, so I think it's a good idea to optimize the common case, but I won't be too disappointed if it's not acceptable. [1] http://lists.qt-project.org/pipermail/development/2011- November/000258.html --

Re: [CMake] [Boost-users] link error in Visual Studio when using boost from CMake

2012-05-01 Thread Rolf Eike Beer
On Di.,  1. Mai. 2012 00:20:58 CEST, Mourad Boufarguine mou...@boufarguine.name wrote: Hi, add this : link_directories(${Boost_LIBRARY_DIRS}) after the include_directories command. No, please don't. The target_link_libraries command is what you really want. Please stop advertising

Re: [CMake] [Boost-users] link error in Visual Studio when using boost from CMake

2012-05-01 Thread Mourad Boufarguine
On Tue, May 1, 2012 at 9:10 AM, Rolf Eike Beer e...@sf-mail.de wrote: On Di., 1. Mai. 2012 00:20:58 CEST, Mourad Boufarguine mou...@boufarguine.name wrote: Hi, add this : link_directories(${Boost_LIBRARY_DIRS}) after the include_directories command. No, please don't. The

Re: [CMake] [Boost-users] link error in Visual Studio when using boost from CMake

2012-05-01 Thread Michael Jackson
On May 1, 2012, at 11:37 AM, Mourad Boufarguine wrote: On Tue, May 1, 2012 at 9:10 AM, Rolf Eike Beer e...@sf-mail.de wrote: On Di., 1. Mai. 2012 00:20:58 CEST, Mourad Boufarguine mou...@boufarguine.name wrote: Hi, add this : link_directories(${Boost_LIBRARY_DIRS}) after

Re: [CMake] [Boost-users] link error in Visual Studio when using boost from CMake

2012-05-01 Thread Hui Wang
Yes, target_link_libraries works well, I had problem before because I used find_package(Boost) instead of find_package(Boost COMPONENTS thread), so when I used target_link_libraries( MyProject ${Boost_LIBRARIES} ), it didn't link anything, after I specify the components in find_package, it has no

[CMake] CMake 2.8.8 bug with cmake-gui and stop button

2012-05-01 Thread Robert Dailey
Remember that change that was made to make pressing stop in cmake-gui more responsive? I'm finding an issue now where during configure, if I stop, it stops without failing, which allows me to press generate on a partial configuration. I'm not sure if this is a bug of feature but I thought I'd

Re: [CMake] CMake 2.8.8 bug with cmake-gui and stop button

2012-05-01 Thread David Cole
It's a bug. You should not be able to generate unless a configure step has *completed* successfully. A good demonstration of the fact that GUI changes are hard to test. On Tue, May 1, 2012 at 4:35 PM, Robert Dailey rcdailey.li...@gmail.com wrote: Remember that change that was made to make

[CMake] configure_file as a build step?

2012-05-01 Thread Jensen, Erik A
I have a JSON file that needs to have some values set based on the project's configuration. During development, this file can change rather frequently. Currently, I am using configure_file to fill in the required values. Unfortunately, every time the file is modified, it triggers CMake to do a

Re: [CMake] math(EXPR) and unary operators

2012-05-01 Thread cowwoc
Apparently this issue is 3 years old: http://public.kitware.com/Bug/view.php?id=8996 Gili Rolf Eike Beer wrote George Koehler wrote: math(EXPR) rejects expressions with negative numbers. This is awful because math() can reject its own negative results. For example, this code fails:

[Cmake-commits] CMake branch, master, updated. v2.8.8-91-g58cc3d1

2012-05-01 Thread David Cole
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 58cc3d1fc41501c00225117d57fcb98d96212b10 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.8-93-gd9427c9

2012-05-01 Thread David Cole
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 d9427c9667bc01fce49d0299115a63867ea25a75 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.8-107-gc75f404

2012-05-01 Thread David Cole
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 c75f404065590d029d91779e4b113340303559f9 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.8-113-g28de112

2012-05-01 Thread David Cole
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 28de11291a257428685eb5739298dfe20b30f795 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.8-117-g99f6055

2012-05-01 Thread David Cole
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 99f6055fe4f047be10ea137e5787418a982596b8 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.8-122-g8df7aa5

2012-05-01 Thread David Cole
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 8df7aa54f0f78d48e4ed91001ac9ac9d39dbf535 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.8-124-g17c65d1

2012-05-01 Thread David Cole
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 17c65d1c443579dfe684d4b354d74407f3d7dc8e (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.8-2784-g0a1547b

2012-05-01 Thread Bill Hoffman
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 0a1547b0f6354c47401e06e361bb24c2041c49f7 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.8-2786-g95157ab

2012-05-01 Thread Bill Hoffman
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 95157abf2b097577d42f990cc3d19148da403465 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.8-2788-g694bafc

2012-05-01 Thread Bill Hoffman
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 694bafcfc3349ea155cb83b93c28c9771b356dbf (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.8-125-g3817314

2012-05-01 Thread Kitware Robot
Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 0908537..6fe9c2b 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 8) -SET(CMake_VERSION_TWEAK 20120501