On 28 November 2016 at 10:19, Thiago Macieira <thiago.macie...@intel.com> wrote: > On domingo, 27 de novembro de 2016 11:52:32 PST Thiago Macieira wrote: >> On domingo, 27 de novembro de 2016 16:29:09 PST Ch'Gans wrote: >> > OK, thanks for spending time on this, I think i will report this to >> > kubuntu, since their 5.6 behaves differently from the official 5.6. >> >> Can you check the compiler command-line flags? Qt 5.6 officially enables >> C++11 for user projects, but it's possible that Ubuntu disabled that. >> >> That would also explain why the feature doesn't work in 5.5. > > Wait, your testcase used a lambda, so C++11 was enabled.
C++ was enabled by default in all 4 configurations, have just tried without C++11 [1], and it didn't make any difference. Ubuntu has enabled c++11, strict_c++, c++14 and c++1z, while official Qt has enabled c++11, strict_c++ and c++14. Could this be the reason why the 2 Qt-5.6 behave differently? Chris [1] using QMAKE_CXXFLAGS = -std=c++98, as CONFIG -= c++11 didn't seem to work) > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
