Will qDebug cost time when CONFIG += console is not set?

Question

qDebug() print out text messages on the console, according to what I know print out text message is expensive. But if I dont set CONFIG += console, will it still cost time? Otherwise I need to comment it one by one by hand?

score 3 · Accepted Answer · edited May 23 '17 at 12:15

3

From Qt documentation:

This function does nothing if QT_NO_DEBUG_OUTPUT was defined during compilation.

So if you want to disable qDebug() in release build, you can add next line to your .pro file (taken from here):

CONFIG(release, debug|release):DEFINES += QT_NO_DEBUG_OUTPUT

See also this question.

edited May 23 '17 at 12:15

Community

1
1

answered May 16 '15 at 16:19

Sam Protsenko

14,045
4
59
75

score 0 · Answer 2 · edited Aug 24 '16 at 13:32

0

qDebug() don't cost any time, even if don't set CONFIG+=console, you can use it for debugging tasks during compilation.

edited Aug 24 '16 at 13:32

Adrian Cid Almaguer

7,815
13
41
63

answered May 16 '15 at 22:28

Jorge Damian Diaz Morejon

62
3

How come that input/output operations don't cost any time? In fact, they take a whole of time. – Sam Protsenko May 16 '15 at 22:51

Will qDebug cost time when CONFIG += console is not set?

2 Answers2