Re: [cmake-developers] [PATCH] remove x placeholder from STREQUAL operands

2014-04-13 Thread Rolf Eike Beer
Am Sonntag, 13. April 2014, 07:05:27 schrieb Jiri Malak: Hi, I enclosed patch for removing placeholder x from STREQUAL operands. It does comparision transparent. I very much would like to see that, but there is a problem: CMake may interpret the operands of STREQUAL both as text and as

Re: [cmake-developers] [PATCH] remove x placeholder from STREQUAL operands

2014-04-13 Thread Jiri Malak
I enclosed patch for removing placeholder x from STREQUAL operands. It does comparision transparent. I very much would like to see that, but there is a problem: CMake may interpret the operands of STREQUAL both as text and as variable name. So this does what you expect for the moment: if

Re: [cmake-developers] [PATCH] remove x placeholder from STREQUAL operands

2014-04-13 Thread Rolf Eike Beer
Am Sonntag, 13. April 2014, 09:59:03 schrieb Jiri Malak: I enclosed patch for removing placeholder x from STREQUAL operands. It does comparision transparent. I very much would like to see that, but there is a problem: CMake may interpret the operands of STREQUAL both as text and as

Re: [cmake-developers] [PATCH] remove x placeholder from STREQUAL operands

2014-04-13 Thread Jiri Malak
Am Sonntag, 13. April 2014, 09:59:03 schrieb Jiri Malak: I enclosed patch for removing placeholder x from STREQUAL operands. It does comparision transparent. I very much would like to see that, but there is a problem: CMake may interpret the operands of STREQUAL both as text and as

Re: [cmake-developers] Problems with CMake-master and OBJECT libraries

2014-04-13 Thread Stephen Kelly
Kevin Funk wrote: I see that there was some discussion wrt this on the cmake ML, [3], but actually I lack the CMake foo in order to understand this discussion's implications. At any rate, I don't think the above behavior is intended, is it? Nope, that's a bug. I've merged a fix into next

[cmake-developers] Learning from the source

2014-04-13 Thread Kevin Ingwersen
Hello everyone! This is my first post here, so hopefuly you can understand me - because I am not a native english speaker! :) As the title suggests, I wish to learn one thing or another. Currently, I am working on a project that has a good bunch of dependencies. They all originate from

[CMake] 2.8/3.0: CMAKE_FORCE_C_COMPILER semantics

2014-04-13 Thread Tim Blechmann
hi all, i'm trying to use the iOS.cmake toolchain file from [1]. it works fine with cmake-2.8.12.2, but fails with cmake-3.0 (today's master), which gives me: --8--- CMake Error at CMakeLists.txt:16 (project): The CMAKE_C_COMPILER: gcc is not a full path and was not found in

Re: [CMake] 2.8/3.0: CMAKE_FORCE_C_COMPILER semantics

2014-04-13 Thread Rolf Eike Beer
Am Sonntag, 13. April 2014, 11:05:44 schrieb Tim Blechmann: hi all, i'm trying to use the iOS.cmake toolchain file from [1]. it works fine with cmake-2.8.12.2, but fails with cmake-3.0 (today's master), which gives me: --8--- CMake Error at CMakeLists.txt:16 (project): The

Re: [CMake] 2.8/3.0: CMAKE_FORCE_C_COMPILER semantics

2014-04-13 Thread Rolf Eike Beer
include (CMakeForceCompiler) CMAKE_FORCE_C_COMPILER (gcc gcc) CMAKE_FORCE_CXX_COMPILER (g++ g++) A more general question: is there any reason one would have to force a compiler in a toolchain file? Just set CMAKE_*_COMPILER to the path, that should be all that is needed, no? I've seen this

[CMake] Who adds -lrt to LINK_LIBRARIES ?

2014-04-13 Thread Adrian M Negreanu
Hi, I'm using android.toolchain.cmake to build a shared library. I'm not linking explicitly with rt anywhere but the lib still gets an -lrt. I assume cmake detects a dependency on -lrt and adds it. Is this true or coming from android.toolchain.cmake ? thanks -- Powered by www.kitware.com

[CMake] Phony target for version 3.0

2014-04-13 Thread Kornel Benko
Trying to use phony target (working with 2.8.12) like add_custom_target(doc0 DEPENDS ${some_dep_files}) leads to error messages like: CMake Error: Could not get source file entry for builddir/CMakeFiles/doc0 Kornel signature.asc Description: This is a digitally

[CMake] cmake - configuration roolback to default

2014-04-13 Thread shahidan
Hi Losif, Yes, this what im looking for. It works! Thank you. I have problem in running make to compile an open source project. Im using virtualbox and my RAM settings in under 500mb. My compilation alway get stuck here: [ 18%] Building CXX object

Re: [CMake] 2.8/3.0: CMAKE_FORCE_C_COMPILER semantics

2014-04-13 Thread Alexander Neundorf
On Sunday, April 13, 2014 12:12:10 Rolf Eike Beer wrote: include (CMakeForceCompiler) CMAKE_FORCE_C_COMPILER (gcc gcc) CMAKE_FORCE_CXX_COMPILER (g++ g++) A more general question: is there any reason one would have to force a compiler in a toolchain file? Just set CMAKE_*_COMPILER to the

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2259-geec8205

2014-04-13 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 eec820547e8ec5d3a8f24d45c6d1a215bd96a85c (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2261-g7cbc305

2014-04-13 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 7cbc305dea72b5b5fe709880b12cbfea70f9a293 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2264-ga7d96ad

2014-04-13 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 a7d96ad6024001e7ae5042210ae033cf4f6cb1e7 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2266-gbd132bd

2014-04-13 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 bd132bd4e82c17a3bb34982be2deadcf8815cbfd (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-rc3-2270-g94d5a91

2014-04-13 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 94d5a919570b7dbb82fa2f45b88f1b57b5d42c8e (commit) via