[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 --