> -----Original Message----- > [...] > So I've supposed the Qt 5.12.0 release (MSVC2017 / 32bit) have been build > with QT_NO_WARNING_OUTPUT and QT_NO_DEBUG_OUTPUT.
That's not the case, at least for the official packages. QT_NO_WARNING_OUTPUT, QT_NO_DEBUG_OUTPUT anyway does only affect the code it was compiled with. That is, qDebug() in your own code shouldn't be affected if Qt itself was compiled with QT_NO_XXX_OUTPUT. > Once again, with previous Qt release, all works as expected. Please try to create a minimal example, and add it to a Qt Support or bugtracker ticket. Regards Kai _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
