[cmake-developers] [CMake 0013893]: CMAKE_OSX_SYSROOT overwritten to /

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

[cmake-developers] [CMake 0013894]: Ninja generator uses relative paths for source files

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=13894 == Reported By:Mika Fischer Assigned To:

[CMake] CMake won't find OpenCV properly

Hey there, I am working on a project with CMake and OpenCV (CUDA and QT too, but that is another story). I am trying to get the FIND_PACKAGE (OpenCV REQUIRED) line working, but unfortunately this line is not exactly working. Although I pointed OpenCV_DIR to H:/opencv/build/x86/vc10/lib

[CMake] Is INSTALL_RPATH Meant to be Relative to CMAKE_INSTALL_PREFIX?

Hi all, I found code that sets LIB_INSTALL_DIR to a relative path (lib or lib64), then later calls FindKDE4Internal.cmake where CMAKE_INSTALL_RPATH is set to LIB_INSTALL_DIR and ultimatelysets the rpath of a library to something containing the relative path lib. Was that relative path meant to be

[CMake] Compatibility between cmake-based directives and autoconf-based directives

Is there a way how to avoid problems with different declarations of directives depending whether using autoconf (for a library) and cmake (for my application using that library). For example autoconf declares #define HAVE_UNISTD_H 1 while cmake declares #define HAVE_UNISTD_H. Using #cmakedefine01

[CMake] Running CPack and ignore exit codes

Hi, when i run cpack, then it breaks after the first error. Is there a way (For NMake for example) to run nmake /I to ignore exit codes and build as much as possible? Thanks in advance -- Powered by www.kitware.com Visit other Kitware open-source projects at

[CMake] CMAKE_OSX_ variables lacking documentation

I was looking for documentation in the CMake manual for CMAKE_OSX_ARCHITECTURES. This is a list of architectures, the possible choices are: i386;x86_64;ppc;ppc64 But this is not mentioned in the CMake documentation. Shouldn't it be? -- Powered by www.kitware.com Visit other Kitware

[CMake] Building CMake 2.8.10.2 -- package created named cmake-2.8.10.2-Darwin-i386.dmg?

Building on OS X 10.7.5 with XCode 4.5.2 Compiling with default compiler Apple clang version 4.1 (tags/Apple/clang-421.11.66) The packages available for download on cmake.org are named http://www.cmake.org/files/v2.8/cmake-2.8.10.2-Darwin64-universal.dmg My question is this: how is the

Re: [CMake] Building CMake 2.8.10.2 -- package created named cmake-2.8.10.2-Darwin-i386.dmg?

Hi Kent, Probably because the CPACK_SYSTEM_NAME is explicitly specified. See http://cmake.org/gitweb?p=cmake.git;a=blob;f=Utilities/Release/dashmacmini5_release.cmake;h=36b095287e80d26ed1b684b6c1a69d9bda1963ba;hb=HEAD#l19 Hth Jc On Tue, Feb 5, 2013 at 9:47 AM, Kent Williams

Re: [CMake] Building CMake 2.8.10.2 -- package created named cmake-2.8.10.2-Darwin-i386.dmg?

What do you mean by it's wrong? It's a universal binary with x86_64 being one of them. On Feb 5, 2013, at 10:04 AM, Jean-Christophe Fillion-Robin jchris.filli...@kitware.com wrote: Hi Kent, Probably because the CPACK_SYSTEM_NAME is explicitly specified. See

Re: [CMake] Building CMake 2.8.10.2 -- package created named cmake-2.8.10.2-Darwin-i386.dmg?

I meant that when I build cmake and then ran 'make package' it cmake out i386, even though by default it only generates 64-bit binaries. Jean-Christophe pointed out that on Kitware's builds they override this with a better CPACK_SYSTEM_NAME. And the reason it says i386 is that CPACK_SYSTEM_NAME

[CMake] FindProtobuf error: _protobuf_include_path empty

Hi all, I've been fighting against this error for the last two hours. When I try to setup a cmake-based project which builds some protobuf related stuff, something strange happens. My sample cmake directives follow: find_package(Protobuf REQUIRED)

Re: [CMake] Building CMake 2.8.10.2 -- package created named cmake-2.8.10.2-Darwin-i386.dmg?

On Tue, 5 Feb 2013 09:22:35 -0600, Kent Williams said: And the reason it says i386 is that CPACK_SYSTEM_NAME defaults to the output of uname -p which on OS X 10.7.5 is 'i386' So CMake is behaving as documented, and OS X is wrong ;-) Quelle Surprise! OS X returns 'i386' for 'uname -p'

Re: [CMake] Building CMake 2.8.10.2 -- package created named cmake-2.8.10.2-Darwin-i386.dmg?

Few pointers talking about the issue: - http://yourmacguy.wordpress.com/2009/08/24/boot-snow-leopard-64-bit/ - http://arstechnica.com/apple/2009/08/mac-os-x-10-6/5/ Hth Jc On Tue, Feb 5, 2013 at 11:00 AM, Sean McBride s...@rogue-research.comwrote: On Tue, 5 Feb 2013 09:22:35 -0600, Kent

[CMake] Release date for CMake 2.8.11?

Hi, does anybody know the new release date for CMake 2.8.11? In Mantis the date was scheduled for 2013-01-30. Thanks in advance -- 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] When should I use add_subdirectory and when ExternalProject?

On Monday 04 February 2013, David Cole wrote: The OpenChemistry project ( https://github.com/OpenChemistry/openchemistry ) is a very good example of a SuperBuild project that builds all of its external dependencies via ExternalProject, and then all of its git submodules (internal dependencies

Re: [CMake] Is INSTALL_RPATH Meant to be Relative to CMAKE_INSTALL_PREFIX?

On Tuesday 05 February 2013, David Narvaez wrote: Hi all, I found code that sets LIB_INSTALL_DIR to a relative path (lib or lib64), then later calls FindKDE4Internal.cmake where CMAKE_INSTALL_RPATH is set to LIB_INSTALL_DIR and ultimatelysets the rpath of a library to something containing

Re: [CMake] Compatibility between cmake-based directives and autoconf-based directives

On Tuesday 05 February 2013, DRypl wrote: Is there a way how to avoid problems with different declarations of directives depending whether using autoconf (for a library) and cmake (for my application using that library). For example autoconf declares #define HAVE_UNISTD_H 1 while cmake

Re: [CMake] When should I use add_subdirectory and when ExternalProject?

Hi Alex, You could probably pass the CMAKE_INSTALL_PREFIX option. For example: https://github.com/Slicer/Slicer/blob/master/SuperBuild/External_DCMTK.cmake#L44 Hth Jc On Tue, Feb 5, 2013 at 1:10 PM, Alexander Neundorf a.neundorf-w...@gmx.netwrote: On Monday 04 February 2013, David Cole

Re: [CMake] When should I use add_subdirectory and when ExternalProject?

-Original Message- From: Alexander Neundorf a.neundorf-w...@gmx.net To: cmake cmake@cmake.org Sent: Tue, Feb 5, 2013 1:09 pm Subject: Re: [CMake] When should I use add_subdirectory and when ExternalProject? On Monday 04 February 2013, David Cole wrote: The OpenChemistry

Re: [CMake] Compatibility between cmake-based directives and autoconf-based directives

That's it. Thank you very much Alex :-) D. -- View this message in context: http://cmake.3232098.n2.nabble.com/Compatibility-between-cmake-based-directives-and-autoconf-based-directives-tp7583105p7583121.html Sent from the CMake mailing list archive at Nabble.com. -- Powered by

Re: [CMake] When should I use add_subdirectory and when ExternalProject?

On Tuesday 05 February 2013, David Cole wrote: -Original Message- From: Alexander Neundorf a.neundorf-w...@gmx.net To: cmake cmake@cmake.org Sent: Tue, Feb 5, 2013 1:09 pm Subject: Re: [CMake] When should I use add_subdirectory and when ExternalProject? On Monday 04 February 2013,

Re: [CMake] Is INSTALL_RPATH Meant to be Relative to CMAKE_INSTALL_PREFIX?

On Tue, Feb 5, 2013 at 1:15 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: I know this was the case at some point in I think the frameworks branch of kdelibs, but this was wrong, and I think it has been fixed. Or where did you see this ? I'm currently using KDE 4.10 RC 2 and, as far as

Re: [CMake] When should I use add_subdirectory and when ExternalProject?

-Original Message- From: Alexander Neundorf a.neundorf-w...@gmx.net To: David Cole dlrd...@aol.com Cc: cmake cmake@cmake.org Sent: Tue, Feb 5, 2013 2:50 pm Subject: Re: [CMake] When should I use add_subdirectory and when ExternalProject? On Tuesday 05 February 2013, David Cole

Re: [CMake] Is INSTALL_RPATH Meant to be Relative to CMAKE_INSTALL_PREFIX?

On Tuesday 05 February 2013, David Narvaez wrote: On Tue, Feb 5, 2013 at 1:15 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: I know this was the case at some point in I think the frameworks branch of kdelibs, but this was wrong, and I think it has been fixed. Or where did you see

Re: [CMake] Is INSTALL_RPATH Meant to be Relative to CMAKE_INSTALL_PREFIX?

On Tue, Feb 5, 2013 at 3:29 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: What exactly are you building ? Is LIB_INSTALL_DIR preset somewhere ? The software in question is GammaRay, see https://github.com/KDAB/GammaRay/blob/master/CMakeLists.txt#L124 where it sets the LIB_INSTALL_DIR

Re: [CMake] Is INSTALL_RPATH Meant to be Relative to CMAKE_INSTALL_PREFIX?

On Tuesday 05 February 2013, David Narvaez wrote: On Tue, Feb 5, 2013 at 3:29 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: What exactly are you building ? Is LIB_INSTALL_DIR preset somewhere ? The software in question is GammaRay, see

[CMake] Linker command line length issues when cross-compiling from Windows-Linux

Hi, I'm using CMake 2.8.10.2 with the Unix Makefiles generator on Windows and cross-compiling for Linux using GCC. I have Cygwin in the path for make/sh/etc. To cross compile I have the following items set: CMAKE_SYSTEM_NAME:STRING=Linux CMAKE_CXX_COMPILER:STRING=path to cross-compiler gcc

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-562-g252209f

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 252209fb0bce4adba20f1aa3971437d336e5d2b0 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-564-g4341fd2

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 4341fd2579d78e72eea8bd9b87a21fa660d69a35 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-569-g08f6932

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 08f69324bb440ea873d78e271a3f360b9c558af7 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-571-gd1660f0

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 d1660f089585ef2e28d918f87d1e6065a444bb2c (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-573-g9ff34ff

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 9ff34ff2fddc4c60737c16b9ace7fd567047da9c (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-575-ge6b72e8

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 e6b72e8b8719f5cd8b7bd8b296c05123c0fb1395 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-577-g252c521

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 252c5211b57e48da87b94a49503f515ef5edbe6f (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-595-g0205258

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 020525845a3999078e4f7897d293c5aeab20af87 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-608-gec85306

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 ec85306025ae787e08d4ce097fde966f1809c74f (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1928-g7856989

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 7856989a47c051df97094010438308beec1762ec (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1942-ga0c8456

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 a0c84560458844f92855dfa82d9f9b6f0854a640 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1944-ga4f81d9

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 a4f81d981e281636ac708bd6bd599a40c01a31d4 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-609-g47eacab

Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 8a54237..10d7634 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 20130205