[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: QT_NO_DEBUG, Q_ASSERT(), and release build types
From:       Armin Berres <trigger () space-based ! de>
Date:       2009-01-13 14:37:31
Message-ID: 20090113143731.GA6159 () bluefire
[Download RAW message or body]

On Tue, 13 Jan 09 00:18, Andreas Hartmetz wrote:
> On Monday 12 January 2009 00:49:59 Armin Berres wrote:
> > On Sun, 11 Jan 09 23:34, Andreas Hartmetz wrote:
> > > Hi all,
> > >
> > > it occurred to me that QT_NO_DEBUG is not defined in RELWITHDEBINFO build
> > > mode. It is defined, since Allen Winter made it so, in RELEASE build
> > > mode. Note that Debian packages and probably others are built with
> > > RELWITHDEBINFO,
> >
> > Oh, and FWIW we don't exactly use RELWITHDEBINFO in Debian. In the end it
> > is RELWITHDEBINFO + -DNDEBUG. IIRC the only reason we don't define
> > QT_NO_DEBUG is that it would disable the kDebug() output.
> >
> Hmm, no controversy about the goal. That's certainly fine with me :)
> 
> Now, does anyone have an idea how to enable QT_NO_DEBUG (or specifically its 
> performance benefits) and still keep debug output enabled? I admittedly did 
> zero research.

I guess it is this part from kdelibs/kdecore/io/kdebug.h:

#if !defined(KDE_NO_DEBUG_OUTPUT)
# if defined(QT_NO_DEBUG) || defined(QT_NO_DEBUG_OUTPUT) || defined(QT_NO_DEBUG_STREAM)
#  define KDE_NO_DEBUG_OUTPUT
# endif
#endif

I don't know how well the stuff in kdelibs/kdecore/io/kdebug.cpp works
if KDE_NO_DEBUG_OUTPUT is not, but QT_NO_DEBUG is defined though...

Greetings,
Armin
[prev in list] [next in list] [prev in thread] [next in thread]