[Development] Removing the -c++11 option from configure

Edward Sutton edward.sutton at subsite.com
Sat Mar 21 19:55:52 CET 2015

When cross-compiling Qt for embedded use, are C++11 compilers always available?

Personally I have avoided using latest  C++11 in my Qt applications.

My concern is that I will need to port a Qt app to an embedded platform that only has no C++11 compilers.  Or perhaps an old Linux distribution such as RHEL 5.


> On Mar 21, 2015, at 1:40 PM, Thiago Macieira <thiago.macieira at intel.com> wrote:
> We'd like to make Qt build unconditionally with the latest version of the C++
> standard that is supported by the compiler. That implies removing the -c++11
> option so that the -no-c++11 option goes away too.
> Possible drawbacks:
> - Inability to test non-C++11 codepaths in the CI
>   => We can add a hidden option for the CI
> - OS X support without libc++ may go away
>   => I need more information on this
> Advantage:
> - Will turn on C++14 for recent GCC and Clang
> Anything I missed? Opinions?
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

This email and any files transmitted with it from The Charles Machine Works, Inc. are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the sender. Our company accepts no liability for the contents of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

More information about the Development mailing list