Hello CMake Developers,
i've recently encountered an issue with the CMake [CMAKE_]C_STANDARD
settings. (same for CXX)
For initial background see
http://public.kitware.com/pipermail/cmake/2015-September/061546.html
Basically, CMake silently continues to configure past any
On 09/15/2015 10:09 AM, David Gobbi wrote:
> The first is trivial, it simply adds Python 3.5 and 3.6 to the search list.
>
> The second removes the long-deprecated PYTHON_INCLUDE_PATH as a suggestion
> for PYTHON_INCLUDE_DIR.
Thanks. I've applied these two:
FindPython{Interp,Libs}: Add
On Wed, Sep 16, 2015 at 7:03 AM, Brad King wrote:
> On 09/15/2015 10:09 AM, David Gobbi wrote:
> > The first is trivial, it simply adds Python 3.5 and 3.6 to the search
> list.
> >
> > The second removes the long-deprecated PYTHON_INCLUDE_PATH as a
> suggestion
> > for
On 09/14/2015 04:16 PM, Brad King wrote:
> I think our path forward here is to teach the Makefile and Ninja
> generators how to add user-specified manifest files to the "mt"
> invocations as outlined above.
I've drafted support for this in all generators, with a test:
Add support for *.manifest
On 09/16/2015 10:00 AM, David Gobbi wrote:
> this new patch only changes the search for the include dirs.
Thanks. Rather than calling find_path twice, the first call could
just use HINTS instead of PATHS. HINTS are meant for this use case:
searching paths detected from the system in some
On 09/16/2015 11:39 AM, Brad King wrote:
> On 09/16/2015 10:00 AM, David Gobbi wrote:
>> this new patch only changes the search for the include dirs.
>
> Thanks. Rather than calling find_path twice, the first call could
> just use HINTS instead of PATHS. HINTS are meant for this use case:
>
Brad King wrote:
> The default dialect computed with the compiler id may not be the
> same as the effective default dialect when CMAKE_CXX_FLAGS is
> considered. One may build with -std=c++11, for example, thus
> making the dialect used for compilation different than the raw
> compiler default
Brad King wrote:
> On 09/16/2015 03:56 AM, Daniel Wirtz wrote:
>> Basically, CMake silently continues to configure past any
>> set(CMAKE_C_STANDARD ) command even if CMake does
>> not have any information on the necessary flags for the current compiler.
>
> For reference, this was discussed
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15747
==
Reported By:James Johnston
Assigned To:
On 09/16/2015 02:22 PM, Stephen Kelly wrote:
>> The default dialect computed with the compiler id may not be the
>> same as the effective default dialect when CMAKE_CXX_FLAGS is
>> considered.
>
> I pushed another fixup which may disable the test in that case, and may also
> disable it with GNU
On 09/16/2015 03:00 PM, Stephen Kelly wrote:
> I ran cmake with -DCMAKE_CXX_FLAGS=-std=c++11.
>
> The result is that a default of 11 is computed (with my branch) for the
> CXX_STANDARD_DEFAULT because of the CMAKE_CXX_FLAGS=-std=c++11,
Right. I forgot that we honor CMAKE__FLAGS for the
Brad King wrote:
> On 09/16/2015 02:22 PM, Stephen Kelly wrote:
>>> The default dialect computed with the compiler id may not be the
>>> same as the effective default dialect when CMAKE_CXX_FLAGS is
>>> considered.
>>
>> I pushed another fixup which may disable the test in that case, and may
>>
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15748
==
Reported By:James Johnston
Assigned To:
Hi,
On 15/09/15 20:24, Stephen Kelly wrote:
> I have merged a Konsole output compute-default-dialect to next for
> testing which implements the automatic detection. Please test it to see
> if it works with xcode 7.
The CompileFeatures test does pass:
$ git describe
v3.3.1-3005-gf1591ef
I
> -Original Message-
> From: Brad King [mailto:brad.k...@kitware.com]
> Sent: Wednesday, September 16, 2015 20:13
> To: James Johnston; 'Gilles Khouzam'
> Cc: cmake-developers@cmake.org
> Subject: Re: [cmake-developers] CMake user-provided manifest files
>
> On 09/16/2015 03:43 PM, James
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15749
==
Reported By:Ilya
Assigned To:
On Wed, Sep 16, 2015 at 9:41 AM, Brad King wrote:
> On 09/16/2015 11:39 AM, Brad King wrote:
> > On 09/16/2015 10:00 AM, David Gobbi wrote:
> >> this new patch only changes the search for the include dirs.
> >
> > Thanks. Rather than calling find_path twice, the first
Steve,
In regard to this topic:
Project: Determine default language dialect for the compiler.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=77691638
fixup! Project: Determine default language dialect for the compiler.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=10e937ad
fixup!
On 09/16/2015 03:56 AM, Daniel Wirtz wrote:
> Basically, CMake silently continues to configure past any
> set(CMAKE_C_STANDARD ) command even if CMake does
> not have any information on the necessary flags for the current compiler.
For reference, this was discussed during the original design in
19 matches
Mail list logo