[SOLVED]Problem with Qt 5.5

SGaist

Hi,

Running 0S X 10.8 and Xcode 5 ?

mcosta

Hi,

I think that you need to add some #include in your sources.
DO you see some message related to your source files?

Huulivoide

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

SGaist

@Huulivoide it's not the same problem, the one from the mailing list is about a warning storm, here those are errors

freddy311082

Thank guys for you answers...

I'm running OS X Yosemite with XCode 6.4...

regards

freddy311082

@mcosta said:

Hi,

I think that you need to add some #include in your sources.
DO you see some message related to your source files?

Hi my friend... why do you say that I'm missing some include ??

regard

sandy.martel23

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++.

mcosta

@freddy311082

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"??

krekeltronics

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

@krekeltronics said:

QMAKE_CXXFLAGS += -std=c++1

Now you can use

CONFIG += c++11

krekeltronics

@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 :)

mcosta

The warnings are related to a bug. Read here