> -----Original Message----- > From: interest-bounces+kai.koehne=digia....@qt-project.org > [mailto:interest-bounces+kai.koehne=digia....@qt-project.org] On Behalf > Of K. Frank > Sent: Tuesday, April 16, 2013 12:19 AM > To: Qt-interest > Subject: Re: [Interest] Several issues compiling Qt 4.8.4 with mingw-w64 > 4.8.1, possible related to "-std=gnu++11" > > [...] > I also have the concern that if I do turn off c++11 when building QtScript / > QtWebKit, even if the Qt build succeeds, I would still expect compiling any of > my own code that jointly uses c++11 and QtScript / QtWebKit to fail because I > am seeing the compilation errors in the header files. Is this a legitimate > concern? If so, is there some way I might work around it?
Actually I'd expect that to work just fine. The commonly reported issue with mixing e.g. -std=c++11 and -std=gnu++98 (the default) is ABI changes in the std:: namespace. Since Qt does use it only sparingly, and in inline methods, IMO you should be fine compiling your app with e.g. std=c++11 and still compile against stock QtScript/QtWebKit. > One more note: I ran configure with "-no-webkit". Do you think that if I > also > add "-no-script" to my configure that I will be able to build Qt with c++11 > turned on? > > I haven't (explicitly) used QtScript. What would I be giving up if I turned > it > off? e.g. QtDeclarative won't compile then. > > Thiago Macieira - thiago.macieira (AT) intel.com > > Software Architect - Intel Open Source Technology Center > > Thanks very much for your advice. > > > K. Frank > _______________________________________________ > 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