[Interest] CONFIG c++2a vs. QMAKE_CXXFLAGS += -std=c++2a

[Michael Corcoran]

Hi Bernhard,

This is documented on the QMake Variable Reference page [0]. strict_c++ disables compiler extensions, so for example if you specify CONFIG += -std=c++2a with GCC [1] you will end up with --std=gnu++2a being passed to the compiler, and with instead CONFIG += -std=c++2a strict_c++ you will get --std=c++2a.

Best Regards,
Michael


[0] https://doc.qt.io/qt-5/qmake-variable-reference.html
[1] https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html --std section

________________________________________
From: Interest <interest-bounces at qt-project.org> on behalf of Bernhard Lindner <private at bernhard-lindner.de>
Sent: Thursday, 7 May 2020 7:01 AM
To: interest at qt-project.org
Subject: Re: [Interest] CONFIG c++2a vs. QMAKE_CXXFLAGS += -std=c++2a

Ok, I see. Thanks a lot Thiago!

Is this documented somewhere?

> > Can somebody please explain the difference between t
> > he following QMAKE
> > project lines when building a GCC project:
> >
> > CONFIG += c++2a
> >
> > QMAKE_CXXFLAGS += -std=c++2a
> >
> > I expected both to have the same effect but there must be a difference since
> > the latter gives me compilation errors while the first does not.
>
> The latter is equivalent to:
>
> CONFIG += c++2a strict_c++

--
Best Regards,
Bernhard Lindner

_______________________________________________
Interest mailing list
Interest at qt-project.org
https://lists.qt-project.org/listinfo/interest