> Raising the minimum Core Language to C++14 for Linux/XCB
Ok, the title was bit misleading. You want to increase for all regular Linux builds. That would be fine for the task I linked earlier. But according to http://doc.qt.io/qt-5/supported-platforms.html Red Hat Enterprise Linux 6.6 does not have GCC 5. ________________________________ From: Development <[email protected]> on behalf of Gatis Paeglis <[email protected]> Sent: Sunday, July 15, 2018 12:17:52 PM To: Thiago Macieira; [email protected] Subject: Re: [Development] Raising the minimum Core Language to C++14 for Linux/XCB > There has been no reply on this subject. Shall I assume silence is consent and > we can begin using C++14 constructs in the XCB plugin? I think I know which patch you are talking about and then my answer is we can't. The code that you are looking at I want to eventually move in some common place (out of XCB) as part of [1]. [1] https://bugreports.qt.io/browse/QTBUG-65503<https://b> ________________________________ From: Development <[email protected]> on behalf of Thiago Macieira <[email protected]> Sent: Saturday, July 14, 2018 4:23:01 PM To: [email protected] Subject: Re: [Development] Raising the minimum Core Language to C++14 for Linux/XCB On Thursday, 5 July 2018 12:53:14 PDT Thiago Macieira wrote: > On Mac, we kinda already require that. I'm asking to raise the minimum for > the regular Linux builds to C++14. Specifically, I'm asking for the "auto" > functions without trailing return type and relaxed constexpr. > > Currently, our minimum supported GCC version is 4.7 (on QNX only) and 4.8 > elsewhere. That would raise the minimum on Linux to GCC 5, as per: > https://gcc.gnu.org/projects/cxx-status.html#cxx14 > > That's a 3-year-old compiler, four releases out of date, present in the > main, binary Linux distros since: > Ubuntu 15.10 [2015] > Fedora 22 [2015] > Debian 9 (Stretch) [2017] > openSUSE Leap 15 [2018] > > Note that this does not apply to QNX or Android, so C++14 features would not > be allowed in cross-platform code. > > But we'd be able to use it in the XCB plugin. [Does QNX build that?] There has been no reply on this subject. Shall I assume silence is consent and we can begin using C++14 constructs in the XCB plugin? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
