Hi all,
I've recently switched from CMake 2.8.12 to 3.2, full of enthusiasm that
header-only libraries would now be better supported through the INTERFACE
option/target. However, the support for header-only libraries isn't really
great, in particular if you're using an IDE like Visual Studio.
The
On 07/09/2015 01:43 PM, Clifford Yapp wrote:
> OK, more info - it looks like the problem is limited to the CMake GUI
> configure (although I haven't been able to test ccmake, the basic
> cmake works) and the test file is pretty simple:
Thanks. I've narrowed it down to this session:
-
On Thu, Jul 9, 2015 at 1:35 PM, Clifford Yapp wrote:
> 3. Have one or a number of variables that will hold in memory all the
> text written out by message (CMAKE_MESSAGES, CMAKE_STATUS_MESSAGES,
> CMAKE_ERROR_MESSAGES, etc.) so the CMakeLists.txt file can create log
> files reflecting what the u
A problem has arisen with CMake and BRL-CAD in 3.3, and it looks like
it may relate to some command overriding BRL-CAD does in order to
support some of our more advanced build features. The feature we are
using to do this is an unsupported debug feature, and Brad King
suggested moving over to cmak
On 07/09/2015 12:59 PM, Robert Goulet wrote:
> Awesome, thanks Brad.
>
> I'm guessing it's too late for 3.3?
Yes ;)
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support t
Awesome, thanks Brad.
I'm guessing it's too late for 3.3?
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Thursday, July 9, 2015 12:55 PM
To: Robert Goulet
Cc: cmake-developers@cmake.org
Subject: Re: [cmake-developers] Generator expressions for output directory/na
On 07/08/2015 04:57 PM, Robert Goulet wrote:
> Ok let's start with the simplest one, OUTPUT_NAME generator
> expressions support, then we'll do the others.
I made one documentation update:
Help: Improve OUTPUT_NAME documentation formatting
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9a1e
Thanks for your feedback, Brad
From: Brad King [mailto:brad.k...@kitware.com]
Sent: 9 июля 2015 г. 18:02
>We'd like to keep testing the default behavior without an explicit toolchain
>file. Also we need to be independent of the toolsets that happen to be
>available on the system where the tes
On 07/09/2015 10:42 AM, Brennan, Sean M wrote:
> See attached git patch.
Applied, thanks:
FindMPI: Extend Intel-MPI 5+ workaround for recent GCCs
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5d7653a0
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMak
On 07/08/2015 09:46 AM, Brad King wrote:
> On 07/08/2015 03:08 AM, darkapos...@rule506.net wrote:
>> C++14 is a first class citizen in Xcode 6.
>
> AppleClang: Use modern C++14 standard flags for Xcode 6
> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d0430c0a
It turns out that the newer f
On 07/08/2015 11:21 AM, Mikhail Filimonov wrote:
> I've extended the Nsight Tegra project generator in CMake and added a bunch
> of properties with the backing variables to fine-tune the generated projects.
Thanks! Here are some comments.
> ---build-options -DCMAKE_SYSTEM_NAME=Android
>
See attached git patch.
FindMPI: Intel-MPI 5+ workaround needs an additional/alternate keyword to
recognize this case with recent GCCs.
Confirmed working with intel-mpi/5.0.1 using gcc/4.4.7, gcc/4.6.1, gcc/4.7.2,
gcc/4.8.2, intel/11.1.072, intel/12.1.5, intel/13.1.3, intel/14.0.4,
intel/15.0.
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15644
==
Reported By:Lectem
Assigned To:
=
13 matches
Mail list logo