Hi Kai,
the example is very simple:
-8<-- DebugTest.pro ----
QT -= gui
CONFIG += c++11 console
CONFIG -= app_bundle
SOURCES += main.cpp
---------------
-8<-- main.cpp ---
#include <QCoreApplication>
#include <QDebug>
int main(int argc, char *argv[])
{
QCoreApplication a(argc, argv);
qDebug() << "Hello Debug";
qWarning() << "Hello Warning";
qCritical() << "Hello Critical";
//return a.exec();
return 0;
}
----
When build and run with 5.4.2, output is
Hello Debug
Hello Warning
Hello Critical
When build and run with 5.4.2, output is
Hello Critical
That's it!
-----Ursprüngliche Nachricht-----
Von: Kai Koehne <[email protected]>
Gesendet: Freitag, 11. Januar 2019 11:00
An: Fabrice Mousset | GEOCEPT GmbH <[email protected]>;
[email protected]
Betreff: RE: Qt 5.12 and debug/warnings messages
> -----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
[email protected]
https://lists.qt-project.org/listinfo/development
