[cmake-developers] [CMake 0014943]: Add an option to cpack to select which component package(s) to generate

2014-05-29 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14943 == Reported By:Thierry Valentin Assigned To:

[cmake-developers] [CMake 0014944]: Add more control over individual components in a component-based configuration

2014-05-29 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14944 == Reported By:Thierry Valentin Assigned To:

[cmake-developers] [CMake 0014945]: Q_WS_* obsolete in QT5 - now it is Q_OS_*

2014-05-29 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=14945 == Reported By:Richard Patek Assigned To:

Re: [cmake-developers] Using reflinks during install phase

2014-05-29 Thread Alessandro Di Federico
On Wed, 28 May 2014 16:17:39 -0400 Brad King brad.k...@kitware.com wrote: On 05/28/2014 01:20 PM, Alessandro Di Federico wrote: Hi, I'm working on a quite big project, namely LLVM. As you can imagine, launching a `make install` it's quite time consuming, in particular in Debug builds.

Re: [cmake-developers] Using reflinks during install phase

2014-05-29 Thread Brad King
On 05/29/2014 08:06 AM, Alessandro Di Federico wrote: OK, I'll come up with a patch. The only thing is that --reflink has been introduced around 2009, in coreutils 7.6 (we are currently at 8.22). Is it OK to assume we have such coreutils or some kind of (build-time?) detection is needed?

Re: [cmake-developers] FindFreetype Patches

2014-05-29 Thread Brad King
On 05/28/2014 10:24 PM, Greg Jung wrote: I found on Linux, FindFreetype is not found because it is invoked the lower-case f'. Propose to change the name to Findfreetype. Call find_package(Freetype) in your project to get the case right. -Brad -- Powered by www.kitware.com Please keep

Re: [cmake-developers] OpenBSD without SONAME

2014-05-29 Thread Brad King
On 05/28/2014 05:19 PM, J Decker wrote: CMake would much rather use full paths rather than -L/-l because of ambiguity problems. I can get around abguity by ordering the order of -L entries.. CMake versions prior to 2.6 always did that. We had no end of trouble with the wrong library files

Re: [cmake-developers] Weird dependency on object files generated elsewhere

2014-05-29 Thread Brad King
On 05/08/2014 02:34 PM, James Bigler wrote: CUDA_FILES = /Users/jbigler/code/FindCUDA/build-cmake-git/src/CMakeFiles/cuda_compile.dir//./cuda_compile_generated_test_bin.cu.o When I try to compile cuda_compile_example I get this, though: make[2]: *** No rule to make target

Re: [cmake-developers] New no-soname-option topic for e.g. Android

2014-05-29 Thread Vadim Zhukov
28.05.2014 20:17 пользователь Nils Gladitz nilsglad...@gmail.com написал: On 28.05.2014 18:01, Vadim Zhukov wrote: I assumed that because people kept removing the soname options for their Android toolchains that SONAMEs aren't supported at all. It however looks like they just can't

[cmake-developers] Compiler feature extensions by default

2014-05-29 Thread Stephen Kelly
Hello, Part of the design of the compile features concept is that it may be used to require compiler extensions. The extensions are enabled by default for GNU and Clang - that is, the option -std=gnu++98 is implied. Passing -std=c++98 disables the extensions, as do other language standard

Re: [cmake-developers] OpenBSD without SONAME (was: New no-soname-option topic for e.g. Android)

2014-05-29 Thread Brad King
On 05/29/2014 12:32 PM, Vadim Zhukov wrote: I was not aware of such issue before that question. :) Yes, paths are written in NEEDED entries if requested, that's what CMake does for external libraries (outside project). Internal libraries are linked by name, though, allowing to relocate the

Re: [cmake-developers] Compiler feature extensions by default

2014-05-29 Thread Brad King
On 05/29/2014 12:50 PM, Stephen Kelly wrote: I recommend we change C{,XX}_EXTENSIONS to 'on-by-default'. The user may still set it to FALSE explicitly in order to use a possible non-extended compile option where available. Fine with me. It matches the compiler behavior of having extensions

[CMake] using gtk2 and gtk3 for different modules

2014-05-29 Thread Markus Lausser
Hello, I am trying to use both gtk2 and gtk3 in one project. The structure of the project (with gtk2 only) is like this: core core gtk2 UI Now I tried to add a new user interface based on gtk3. core core gtk2 UI core gtk3 UI The file CMakeLists.txt of core gtk3 UI looks basically like

Re: [CMake] ExternalPackage_Add with Non-CMake project that runs differently then equivalent shell script

2014-05-29 Thread David Cole
Chad, What is the value of CMAKE_BUILD_TOOL? i.e. output of: message(STATUS CMAKE_BUILD_TOOL='${CMAKE_BUILD_TOOL}') Why are you using ${CMAKE_BUILD_TOOL} anyhow when the command lines you're giving will only work with 'make'? -- Powered by www.kitware.com Please keep messages on-topic

Re: [CMake] Use of variables in generator expressions

2014-05-29 Thread David Cole
It's allowed, but it will have the value of target_name from the context of the CMake configure process. (i.e. ${target_name} is evaluated at configure time, and then the evaluated result is what's used at generate time within the generator expression.) HTH, David C. -- Powered by

Re: [CMake] Problem with CMake 2.8.12.2 on Mac OS X

2014-05-29 Thread Robert Bielik
Dammit. Went through all the option files etc. and found the darn -s. Sorry for the noise everyone... /R Brad King skrev 2014-05-28 19:03: On 05/27/2014 09:08 AM, Robert Bielik wrote: Does anyone use CMake on Mac with Xcode 5 (LLVM) ? I cannot get rid of the -s option to the linker (Release)

Re: [CMake] ExternalPackage_Add with Non-CMake project that runs differently then equivalent shell script

2014-05-29 Thread Chad Balen
Hi David, My output is: CMAKE_BUILD_TOOL='/usr/bin/gmake' I was originally using cd path/to/build/directory make #For some reason it doesn't recognize the make command if I leave out the path to the build directory but if you saw in the previous posts, Norman suggested to use

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc6-3426-g1045761

2014-05-29 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 10457616e8d2dd85d6a2f68d6ddfcd908fe94e88 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc6-3428-g11a357d

2014-05-29 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 11a357d370f318892b1ca3ed08bde02e5ba85c9f (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc6-992-g177d0ef

2014-05-29 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 177d0ef15e2767da5dd4774cc9a8d62b14990d2e (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc6-987-g1468e98

2014-05-29 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 1468e986e1874f7c011e74885e4df2fbab65b396 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc6-996-g8afbb34

2014-05-29 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 8afbb346c67c60dcf9383f5e58307d629eafb855 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc6-990-g0fbec3d

2014-05-29 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 0fbec3d3c2a55d40d2671990ffd6baa53dce24d1 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc6-994-g7e011a3

2014-05-29 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 7e011a3db33b7979906482776c3747b42e1d2887 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc6-3435-gfcd3714

2014-05-29 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 fcd3714aa0a5824072994a78377dfbcc7f4c0762 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc6-3438-g2728f8a

2014-05-29 Thread Peter Kuemmel
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 2728f8ab9c12a2d38eeb504c4148acbed5c70c66 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-rc6-997-gc4a26b7

2014-05-29 Thread Kitware Robot
20140529) +set(CMake_VERSION_PATCH 20140530) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake