On Mon, Apr 30, 2018 at 3:30 PM Stephen Kelly wrote:
> On 04/20/2018 01:39 AM, David Blaikie wrote:
>
> Hi there,
>
> I'm experimenting with creating examples (& potential changes to CMake
> itself, if needed/useful) of building clang modules (currently using the
> semi-backwards compatible "head
Well, I am specifying:
set(CMAKE_CXX_STANDARD_REQUIRED ON)
set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_EXTENSIONS ON)
and the compiler line contains “-std=gnu++1y”. I’m using a very recent source
build of CLang and libc++. Any idea why cmake would fall back to 1y in this
case?
> On May 6, 2
Note that c++17 is c++1z. c++1y was C++14.
---
Jean-Michaël Celerier
http://www.jcelerier.name
On Sun, May 6, 2018 at 5:00 PM, Andrew Brownsword <
andrew.e.brownsw...@gmail.com> wrote:
> Hi,
>
> Is there a way to get cmake 3.11 to emit 17 vs 1y when setting
> CMAKE_CXX_STANDARD? I’m findi
Am Sonntag, 6. Mai 2018, 08:00:14 schrieb Andrew Brownsword:
> Hi,
>
> Is there a way to get cmake 3.11 to emit 17 vs 1y when setting
> CMAKE_CXX_STANDARD? I’m finding that it seems to be a common practice to
> use the value of the preprocessor define __cplusplus (which is a date), and
> the valu
Hi,
Is there a way to get cmake 3.11 to emit 17 vs 1y when setting
CMAKE_CXX_STANDARD? I’m finding that it seems to be a common practice to use
the value of the preprocessor define __cplusplus (which is a date), and the
value differs depending on whether 17 or 1y is used (at least with CLang).
