Hello all,
Please review the topic ExternalProject_labels.
---
ExternalProject: Set LABELS property to targets
his is useful for using CDash subprojects.
http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=8810ddb3b710abf222f23ae96ac025beae63d812
---
ExternalProject: Set FOLDER
ExternalProject: Set LABELS property to targets
his is useful for using CDash subprojects.
ExternalProject: Set FOLDER property to targets
This is useful when using the USE_FOLDERS global property
Seems like something this simple is not quite flexible enough to make
it worthwhile. You could
On 04/28/2014 01:07 PM, Brad King wrote:
It looks like in this case users will have to tell Xcode what tool
to use up front using the CMake generator toolset feature (cmake -T).
I think this is acceptable because it only affects old Xcode versions.
Otherwise we will need a much more
On Tuesday, April 29, 2014 11:01:06 AM Brad King wrote:
On 04/28/2014 01:07 PM, Brad King wrote:
It looks like in this case users will have to tell Xcode what tool
to use up front using the CMake generator toolset feature (cmake -T).
I think this is acceptable because it only affects old
On Monday, April 28, 2014 10:26:56 James Bigler wrote:
-Original Message-
From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On
Behalf Of Brad King
Sent: Wednesday, April 23, 2014 11:06 AM
To: cmake-developers@cmake.org
Subject: Re: [cmake-developers] CMP0043
On Monday, April 28, 2014 13:39:09 Brad King wrote:
On 04/28/2014 01:26 PM, James Bigler wrote:
I thought the purpose of policies was to keep some backward compatibility
feature, but allow users to select the new behavior.
The purpose is to change CMake interfaces or behavior while still
On 04/29/2014 04:25 PM, Alexander Neundorf wrote:
Or, you could fix your project to not use the behavior deprecated
by the policy.
Other reasons are e.g. avoiding to annoy your developer team by warnings
which
don't matter (the build has been working, so there's no need to change it).
On Tue, Apr 29, 2014 at 22:59:50 +0200, Alexander Neundorf wrote:
I was talking in general about these warnings. Typically some project
has a working build system (...otherwise it wouldn't build), and after
updating cmake, warnings appear. Since the build is working, there is
no immediate need
On Tue, Apr 29, 2014 at 22:31:27 -0400, Ben Boeckel wrote:
Actually, should 3.0 warn about cmake_minimum_required(VERSION 2.4.0)?
Silly me; 2.4.0 behavior is dropped and 2.2 does indeed warn. :)
--Ben
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
