rums or inter...@qt-project.org.
>
> Regards
>
> Kai
>
> > -----Original Message-
> > From: Development On Behalf Of
> > Fabrice Mousset | GEOCEPT GmbH
> > Sent: Friday, January 11, 2019 9:50 AM
> > To: development@qt-project.org
> > Subject:
Kai Koehne (11 January 2019 10:33) wrote
> 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.
Note that thi
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
#include
int main(int argc, char *argv[])
{
QCoreApplication a(argc, argv);
qDebug() << "Hello Debug";
> -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 i
ercial customer), or use the
forums or inter...@qt-project.org.
Regards
Kai
> -Original Message-
> From: Development On Behalf Of
> Fabrice Mousset | GEOCEPT GmbH
> Sent: Friday, January 11, 2019 9:50 AM
> To: development@qt-project.org
> Subject: [Development] Qt 5.12 a
rcial customer), or use the
forums or inter...@qt-project.org.
Regards
Kai
> -Original Message-
> From: Development On Behalf Of
> Fabrice Mousset | GEOCEPT GmbH
> Sent: Friday, January 11, 2019 9:50 AM
> To: development@qt-project.org
> Subject: [Development] Qt 5
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 a
