QT_NO_DEBUG, Q_ASSERT(), and release build types

[Andreas Hartmetz]

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.