[Development] Qt5 release integration build
Friedemann.Kleint at digia.com
Wed Dec 11 13:30:15 CET 2013
>I suppose that the warnings in the list beneath are still unsolved. Is
>How critical is it to solve those warnings? If they are critical for
the release, I want to give a helping hand to remove them (after all
there are more than 900, the >list below is a synopsis).
The libraries and examples should be fairly clean; we keep an eye on it
(MSVC2012 or MinGW64, typically). Fixing all warnings in the tests is a
different matter. Warnings there are not that critical and things like
'unsafe std::copy()' or similar can be safely be ignored there.
Talking about tests: The test .pro-files still have a lot of DEFINES +=
QT_DISABLE_DEPRECATED_BEFORE=0 . Getting rid of those (unless the test
actually tests deprecated API) is IMO more important than fixing other
warnings since that is going to hit us at some point (in Qt 6 at the
The usual technique for fixing warnings is to push one change per
warning type for easier review (for example, fix all signed/unsigned
comparisons in one change).
More information about the Development