windeployqt - Able to see console while running the application

[Tim.Jenssen]

remove "CONFIG += console" from your .pro file

[Sandhiya]

@Tim.Jenssen I am not using that in the .pro file. Still I am able to see the consolwwhile running the standalone application.

[SGaist]

Hi,

How did you configure your application ?
How are you doing logging in it ?
What version of Qt are you using ?
What version of Windows are you running ?

[Sandhiya]

@SGaist Logging using console.log
Qt creator version : 4.7.2
Qt version: 5.11.1
windows 10

[dheerendra]

You are doing the logging from QML. You can disable the console.log using the following environment variable. Do the following. It will disable the logging.
QT_LOGGING_RULES = qml=false

[Sandhiya]

@dheerendra Where should I set this environmental variable. In .pro file or anywhere else?

[dheerendra]

@dheerendra said in windeployqt - Able to see console while running the application:

QT_LOGGING_RULES

Set in the build environment of Qt Creator. Click on the projects on the left side bar. Select the appropriate kit. Go to Run settings. You will see vars like QTDIR, LOGNAME etc. Set the logging rule here.

[Sandhiya]

@dheerendra Variable:QT_LOGGING_RULES
Value:qml=false
Am I right?

[dheerendra]

Yes. It is right

[Sandhiya]

@dheerendra I tried setting the environmental variable, but still getting the console log along with the standalone application deployed using windeployqt tool.

[J.Hilk]

@Sandhiya
did you do a complete rebuild? Delete the build folder or clean and rerun qmake

if you add

DEFINES += QT_NO_DEBUG_OUTPUT

inside your profile it will disable qDebug() outputs, I'm however not sure if this also effects QML.

[Sandhiya]

@J.Hilk Yeah tried complete rebuild.Still the same.
DEFINES += QT_NO_DEBUG_OUTPUT has no effect on QML.Tried that one too

[dheerendra]


[Sandhiya]

@dheerendra I tried the same as mentioned in the above image. Still the same behavior.

[dheerendra]

Did you run qmake once after setting this parameter ?

[Sandhiya]

@dheerendra Yes I did.

[Sandhiya]

Able to figure out where exactly the problem is. The problem occurs because of adding
QT += qmltest
in .pro file. If I remove the above statement and try to build a standalone exe using windeployqt tool , only the application is getting launched without any console.
Can anyone help in solving this problem without commenting qmltest?

[raven-worx]

@Sandhiya said in windeployqt - Able to see console while running the application:

Can anyone help in solving this problem without commenting qmltest?

why do you need this option when building a release application in the first place?

[Sandhiya]

@raven-worx It's not needed. But when I try building the application in release mode /debug mode that flag by default will be there as part of my .pro file. Is there any way that can be ignored while build a release application?

[raven-worx]

@Sandhiya said in windeployqt - Able to see console while running the application:

But when I try building the application in release mode /debug mode that flag by default will be there as part of my .pro file.

not in common. What flags do you also add to the QT variable in your .pro file?

@Sandhiya said in windeployqt - Able to see console while running the application:

Is there any way that can be ignored while build a release application?

CONFIG(release, debug|release) {
  QT -= qmltest
}

But since you anyway do not need it simply remove it for all configurations.