[SOLVED]Problem with Qt 5.5
-
guys, I have my project with qt 5.4.2 and all is fine, but when I try to compile with qt 5.5 i have plus than 100 error with messages like this and I don’t have any idea what happen:
/Applications/Qt/5.5/clang_64/lib/QtCore.framework/Headers/qstring.h:1310:13: error: no type named 'u16string' in namespace 'std'
/Applications/Qt/5.5/clang_64/lib/QtCore.framework/Headers/qstring.h:1311:15: error: no member named 'u16string' in namespace 'std'
{ return std::u16string(reinterpret_cast<const char16_t*>(utf16()), length()); }/Applications/Qt/5.5/clang_64/lib/QtCore.framework/Headers/qstring.h:1310:13: error: no type named 'u16string' in namespace 'std'
inline std::u16string QString::toStdU16String() const/Applications/Qt/5.5/clang_64/lib/QtCore.framework/Headers/qstring.h:1313:53: error: no type named 'u32string' in namespace 'std'
inline QString QString::fromStdU32String(const std::u32string &s)/Applications/Qt/5.5/clang_64/lib/QtCore.framework/Headers/qstring.h:1318:10: error: no member named 'u32string' in namespace 'std'
std::u32string u32str(length(), char32_t(0));/Applications/Qt/5.5/clang_64/lib/QtCore.framework/Headers/qcompilerdetection.h:1007:43: note: expanded from macro 'Q_DECL_NOEXCEPT_EXPR'
# define Q_DECL_NOEXCEPT_EXPR(x) noexcept(x)
^
/Applications/Qt/5.5/clang_64/lib/QtCore.framework/Headers/qpair.h:42:17: note: declared here
template <class T1, class T2>Someone know about it ??
regards
-
Hi,
Running 0S X 10.8 and Xcode 5 ?
-
This might actually be a different problem, but in any case.
There is some bug in Qt 5.5 and OSX. Fixed in 5.5.1.
See the mailing list for more information.
http://lists.qt-project.org/pipermail/interest/2015-July/017543.html -
@Huulivoide it's not the same problem, the one from the mailing list is about a warning storm, here those are errors
-
Thank guys for you answers...
I'm running OS X Yosemite with XCode 6.4...
regards
-
Those errors are all about C++11 constructs. You probably have some config in your .pro file trying to force an older C++ standard.
Like removing C++11 or forcing stdlibc++ instead of libc++. -
Hi had a very similar problem when I moved my code from Qt 5.3 to 5.4; sometimes some #include are removed from Qt header files and the is needed to add in our code.
Last question: "Are you compiling using C++11"??
-
we are having the same issue on our build server (and yet different errors on the Windows side), and are indeed compiling with C++11. I have QMAKE_CXXFLAGS += -std=c++11 in the .pro file. Is that no longer correct/necessary?
-
-
@mcosta said:
CONFIG += c++11
thanks. That resolved the C++11 errors (and should work for you as well @freddy311082 ). I've got a few other std-related things that didn't appear with the previous version, so I will post back if these seem to be core-related vs. necessary changes in our own code.
I do have the hundreds of
clang diagnostic ignored "-Winconsistent-missing-override"
now :)