QT_NO_DEBUG, Q_ASSERT(), and release build types

Andreas Hartmetz ahartmetz at gmail.com
Sun Jan 18 19:31:53 CET 2009

On Sunday 18 January 2009 16:52:29 Allen Winter wrote:
> On Sunday 18 January 2009 4:04:33 am Thiago Macieira wrote:
> > Allen Winter wrote:
> > >I am undecided if kDebug+qDebug should be on for relwithdebinfo.
> > >I defer to the packagers on that one.
> >
> > qDebug should be off.
> >
> > kDebug, however, could be left on, but with all debug areas turned off.
> > Applications should be silent in release mode (any release mode) unless
> > the output is of interest to the user.
> To summarize the changes:
> 1) disable asserts in release and relwithdebinfo
> 2) disable qDebug in release and relwithdebinfo
> 3) enable kDebug in release and relwithdebinfo if we can turnoff debug
> areas
> Andreas, does that just about cover it?
> Any objections to this plan?
I agree completely. Especially after talking to some people about it on IRC 
this looks like the right solution.
It would be nice to be able to disable qDebug() at runtime but a) it's not 
possible and b) there are *very* few of them.
Only if b) wasn't true I'd try to look for a solution for a).

More information about the Kde-buildsystem mailing list