On 6/13/12 2:59 PM, Stephen Chu wrote: > On 6/13/12 2:49 PM, bradley.hug...@nokia.com wrote: >> This is a new error that we also stumbled over today. Essentially, we can't >> enable C++11 language support in the compiler while the C++ library doesn't >> provide C++11 headers or features. It's all or nothing. > > There are some other errors involving constexpr in some Qt headers too: > https://bugreports.qt-project.org/browse/QTBUG-25817
I mean when using libc++ with clang 3.1 > >> To deal with this, we'll have to introduce a way to switch the C++ runtime >> when building for Mac OS X. The best option to do this is with a new mkspec. >> I have a commit that needed testing (i.e. I started the compile before I >> left work today). I'll upload the commits to Gerrit tomorrow. >> > > So basically once C++11 features are enabled, there's no way to deploy > the built app to OS X 10.6 since there's no libc++ there? > > Also we will have to build Qt itself with libc++ linkage since we do > want the resulting app to link against two different C++ runtime > libraries. Right? I mean we *don't* want to link against two different C++ runtime. Gee. Really need my afternoon coffee now... _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
