Hi Kai, I've used the development mailing list because I think this is a bug in the release. When I build my application with Qt 5.4.2, Qt 5.6.x or Qt 5.11.2 all works as expected. But with Qt 5.12.0, nothing works. Only qCritical() messages are working.
To be more explicit, I use qInstallMessageHandler() to register my logger callback function. The callback method is only called (with Qt 5.12.0) when qCritical() is used. qDebug() and qWarning() have no effect! 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. Once again, with previous Qt release, all works as expected. Regards Fabrice -----Ursprüngliche Nachricht----- Von: Kai Koehne <[email protected]> Gesendet: Freitag, 11. Januar 2019 10:34 An: Fabrice Mousset | GEOCEPT GmbH <[email protected]>; [email protected] Betreff: RE: Qt 5.12 and debug/warnings messages Hi Fabrice, There's been no such change. Your problem is most likely one of two: - You actually disable the qDebug, qWarning via custom logging rules. See http://doc.qt.io/qt-5/qloggingcategory.html , section "Logging Rules" for the details. - You have a GUI program that logs to the system wide debugging log, but other IDE's or debuggers are interfering. Make sure that you don't run multiple IDE's or debuggers at the same time. In general, this is the wrong mailing list for questions about Qt itself. Please contact either support (if you're a commercial customer), or use the forums or [email protected]. Regards Kai > -----Original Message----- > From: Development <[email protected]> On Behalf Of > Fabrice Mousset | GEOCEPT GmbH > Sent: Friday, January 11, 2019 9:50 AM > To: [email protected] > Subject: [Development] Qt 5.12 and debug/warnings messages > > Hi, > > > > I have installed Qt 5.12.0 for Windows / MSVC2017-32bit with Qt > Maintenance Tool. > > I wondering why qDebug and qWarning have been disabled in this version? > > qDebug() and qWarning() do not work, even in Debug build! Why? > > Is this intentional? > > > > Do I have to build Qt from sources to made them work again or will > this be fixed/changed in next build (Qt 5.12.1)? > > > > Regards > > > > Fabrice Mousset _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
