Re: [cmake-developers] TARGET availability

2013-03-22 Thread Vittorio Giovara
On Thu, Mar 21, 2013 at 7:46 PM, Brad King brad.k...@kitware.com wrote: On 03/21/2013 08:11 AM, Vittorio Giovara wrote: similar procedure as found in cmMakefileExectuableTargetGenerator. The logic to compute the actual target file location is more complicated in order to support OS X

[cmake-developers] [CMake 0014035]: list(LENGTH ...) stops counting on special entries

2013-03-22 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=14035 == Reported By:Ove Sommer Assigned To:

[cmake-developers] Issuing errors for faulty INTERFACE_INCLUDE_DIRECTORIES (Was: CMake usage requirements in KDE Frameworks)

2013-03-22 Thread Stephen Kelly
Alexander Neundorf wrote: With PUBLIC, PRIVATE and INTERFACE, directories can be added to the wrong one (i.e. PUBLIC instead PRIVATE or INTERFACE) and it will still build, but the interface will be bigger than necessary. Would it be reasonable to issue an error at install(EXPORT)-time if

Re: [cmake-developers] TARGET availability

2013-03-22 Thread Brad King
On 03/22/2013 04:38 AM, Vittorio Giovara wrote: difference I see is that TARGET in the _LINK_EXECUTABLE or _CREATE_SHARED_LIBRARY gets reported as a relative path, while in _COMPILE_OBJECT you get the full path. Oops, I had copied the TargetPDB path conversion which needs to be full path for

Re: [cmake-developers] Issuing errors for faulty INTERFACE_INCLUDE_DIRECTORIES (Was: CMake usage requirements in KDE Frameworks)

2013-03-22 Thread Brad King
On 03/22/2013 07:14 AM, Stephen Kelly wrote: Would it be reasonable to issue an error at install(EXPORT)-time if the INTERFACE_INCLUDE_DIRECTORIES of a target contains paths in the source dir or binary dir, if the install prefix is not inside one of those itself? Yes, though it won't be able

Re: [cmake-developers] TARGET availability

2013-03-22 Thread Vittorio Giovara
On Fri, Mar 22, 2013 at 12:55 PM, Brad King brad.k...@kitware.com wrote: On 03/22/2013 04:38 AM, Vittorio Giovara wrote: difference I see is that TARGET in the _LINK_EXECUTABLE or _CREATE_SHARED_LIBRARY gets reported as a relative path, while in _COMPILE_OBJECT you get the full path.

[cmake-developers] [Generator] Android.mk

2013-03-22 Thread Thomas Richard
Hi everyone, I am trying to build a set of libraries as part of the android source tree. Being able of using a android.mk generator would be the perfect solution. My current approach is to use a toolchain, as opencv is doing. This is not particularly suitable because a toolchain has to be

[cmake-developers] [CMake 0014037]: target_compile_definitions empty $CONFIGURATION generator

2013-03-22 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=14037 == Reported By:Andreas Stahl Assigned To:

[CMake] How to using 'conditional statements at generate time'?

2013-03-22 Thread Yuchen Deng
hi, there! I was reading the release log in here: http://www.kitware.com/news/home/browse/CMake?2012_11_07CMake+2.8.10+Just+Released Add see the parts: Generator expressions, which are used to introduce conditional statements at generate time rather than at CMake compile time, are now available

Re: [CMake] How to using 'conditional statements at generate time'?

2013-03-22 Thread Stephen Kelly
Yuchen Deng wrote: hi, there! I was reading the release log in here: http://www.kitware.com/news/home/browse/CMake? 2012_11_07CMake+2.8.10+Just+Released Add see the parts: Generator expressions, which are used to introduce conditional statements at generate time rather than at CMake

[CMake] Configure custom build rule to use cuda runtime API build rule

2013-03-22 Thread landa
Hi all, I have a visual studio solution created by a cmake file and I need to modify one project custom build rule to use the CUDA Runtime API Build Rule. If someone knows how I can set the custom build rule directly from my cmake file it will be very helpful. In other words, I want to do :

Re: [CMake] How to using 'conditional statements at generate time'?

2013-03-22 Thread Yuchen Deng
Thanks for your help! It's works, and it seems great!! I just try this command using 2.8.11-rc1: target_include_directories(${target_php} PRIVATE ${CMAKE_CURRENT_SOURCE_DIR};${CMAKE_CURRENT_BINARY_DIR}/SWIG; ${PHP5_INCLUDE_PATH} ) It's cool! 2013/3/22 Stephen Kelly steve...@gmail.com

Re: [CMake] 2.8.11rc1 CMAKE_LINKER and CMAKE_OBJCOPY sporadically vanishing

2013-03-22 Thread Nils Gladitz
I think I found the problem. My client script wrote a new CMakeCache.txt (with initial settings) on every run and therefor also overwrote it in continuous builds if it already existed. In prior CMake versions this seemed to have worked but I'm guessing now some piece of information is made

[CMake] Explicit NAME_LIBRARIES and NAME_INCLUDE_DIRS

2013-03-22 Thread Mateusz Loskot
Hi, I'm trying to build software which uses libE57 library which has Xerces as dependency. I build Xerces too as part of my project and I deploy it in custom locations and Xerces library has custom name. libE57 provides FindXerces.cmake [1] and I've been trying to figure out how I can make this

Re: [CMake] Is there an easy way to time how long build parts take.

2013-03-22 Thread Matthew Woehlke
On 2013-03-21 14:11, Miller Henry wrote: Our build it taking a long time, (15+ minutes even when with a massive build farm to distribute compiles across), and the question keeps coming up: what is actually taking so long. Is there an easy way to measure? If you are using ninja

Re: [CMake] Explicit NAME_LIBRARIES and NAME_INCLUDE_DIRS

2013-03-22 Thread Sergei Nikulov
2013/3/22 Mateusz Loskot mate...@loskot.net Hi, I'm trying to build software which uses libE57 library which has Xerces as dependency. I build Xerces too as part of my project and I deploy it in custom locations and Xerces library has custom name. libE57 provides FindXerces.cmake [1] and

Re: [CMake] change source which does not trigger rebuild ?

2013-03-22 Thread Matthew Woehlke
On 2013-03-13 09:22, Martin Koller wrote: I'd like to solve the following problem, but have not found a way how to yet: Our source is rebuilt every night, but only if some sources changed (e.g. the build tree is not removed, only the source tree is updated from CVS). What I want is to include

Re: [CMake] Explicit NAME_LIBRARIES and NAME_INCLUDE_DIRS

2013-03-22 Thread Andreas Stahl
Am 22.03.2013 um 16:59 schrieb Mateusz Loskot mate...@loskot.net: Hi, I'm trying to build software which uses libE57 library which has Xerces as dependency. I build Xerces too as part of my project and I deploy it in custom locations and Xerces library has custom name. libE57

[CMake] does target_include_directories support SYSTEM?

2013-03-22 Thread Matthew Woehlke
See subject. I have a target that is the compiled sources from some stuff generated by Google Protobuf, which means using the headers also depend on ${PROTOBUF_INCLUDE_DIRS}. I would like to have this be a SYSTEM include... is this supported? Also, is there a way to treat all interface

Re: [CMake] Explicit NAME_LIBRARIES and NAME_INCLUDE_DIRS

2013-03-22 Thread Mateusz Loskot
On 22 March 2013 18:01, Sergei Nikulov sergey.niku...@gmail.com wrote: 2013/3/22 Mateusz Loskot mate...@loskot.net I'm trying to build software which uses libE57 library which has Xerces as dependency. I build Xerces too as part of my project and I deploy it in custom locations and Xerces

Re: [CMake] Explicit NAME_LIBRARIES and NAME_INCLUDE_DIRS

2013-03-22 Thread Mateusz Loskot
On 22 March 2013 21:25, Andreas Stahl andreas.st...@tu-dresden.de wrote: Am 22.03.2013 um 16:59 schrieb Mateusz Loskot mate...@loskot.net: I'm trying to build software which uses libE57 library which has Xerces as dependency. I build Xerces too as part of my project and I deploy it in custom

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2604-gb147ee4

2013-03-22 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 b147ee469aa9ff4f7db106495249461b8bfc3644 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2608-gb3cb0fd

2013-03-22 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 b3cb0fd09db2416f050cf6170559a41cbf9e094d (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2610-g1ca0b5a

2013-03-22 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 1ca0b5a0307774214b9082d168f74b2a8c876e3c (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-922-gd4a94b8

2013-03-22 Thread Kitware Robot
Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index d3bbf1e..f2d3c50 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 20130322