[Development] Removing the -c++11 option from configure
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@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Changes to continuous integration in qtdeclarative/dev
On Thursday 19 March 2015 13:16:43 Frederik Gladhorn wrote: If you run into trouble or see suspicious behavior, talk to Simon, Lars and me, we'll all be keeping an eye on things running smoothly. Great job guys! -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Removing the -c++11 option from configure
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. -Ed On Mar 21, 2015, at 1:40 PM, Thiago Macieira thiago.macie...@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@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. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Removing the -c++11 option from configure
On Saturday 21 March 2015 18:55:52 Edward Sutton wrote: When cross-compiling Qt for embedded use, are C++11 compilers always available? Yes, of course. Embedded targets use GCC too. But that's not relevant to this discussion. 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. RHEL 5 is already not supported and hasn't been since Qt 5.0. That's irrelevant for this discussion. Let me clarify what I said: We'd like to make Qt build unconditionally with the latest version of the C++ standard that is supported by the compiler. That means detecting what's supported and turning it on. I am not saying we will stop supporting compilation in C++98 mode for compilers that don't support C++11. I meant that we will turn C++11 support unconditionally if the compiler supports it. In other words, if you have GCC 4.4 or higher, you won't be able to compile Qt in C++98 mode. The question is: why would you want to? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
