QT_NO_DEBUG, Q_ASSERT(), and release build types

Armin Berres trigger at space-based.de
Sat Jan 24 21:16:16 GMT 2009


On Sat, 24 Jan 09 21:37, Andreas Hartmetz wrote:
> > I don't think keeping kDebug() enabled in release builds is a good idea
> > because of highly likely performance problems. At least, not if logging
> > kDebug() messages is turned on by default. If logging of debug messages
> > was enabled but turned off by default and could easily be turned on by
> > the user if necessary (e.g. through kdebugdialog) then I would agree
> > that enabling it even in release builds would probably be a good idea.
> >
> Committed like that, revision 916186.
> You can see the whole diff here:
> http://mercurial.intuxication.org/hg/kdelibs/rev/287994f46c5d

Cool, thanks.
Kdebugdialog should also be patched now, shouldn't it? Right now it
would enable all the debug output which is not really, what we want.
Debian patch:
<http://svn.debian.org/wsvn/pkg-kde/branches/kde4.2/packages/kdebase-runtime/debian/patches/04_disable_debug_by_default.diff>

Greetings,
Armin




More information about the kde-core-devel mailing list