QT_NO_DEBUG, Q_ASSERT(), and release build types

[Andreas Hartmetz]

On Sunday 25 January 2009 19:36:31 Armin Berres wrote:
> On Sun, 25 Jan 09 11:01, Thiago Macieira wrote:
> > Armin Berres wrote:
> > >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-run
> > >time/debian/patches/04_disable_debug_by_default.diff>
> >
> > I guess you meant this one:
> >
> > http://svn.debian.org/wsvn/pkg-
> > kde/branches/kde4.2/packages/kdelibs/debian/patches/09_disable_debug_mess
> >ages_if_not_explicitly_enabled.diff
>
> No, the above one is more or less what we have in trunk now. This
> problem is fixed.
> There is a problem with kdebugdialog now if kdelibs has been built as
> release build: It show all debug areas as active, though they are
> deactivated.
> I see two solutions: Patch kdebugdialog to just show them as active when
> kdelibs has been built as debug build (how does -runtime know about
> the way kdelibs has been built?), or as you propose install a kdebugrc
> for release builds which explicitly deactivates the all and every debug
> area. I don't really like the second solution, but I also don't really
> care.
>
Option three, committed in revision 917098:
Show checkboxes as half-checked when the debug area has no setting. This works 
because settings for a debug area are only saved when one actually clicks a 
checkbox to change it.
Is that okay for everybody?

Cheers,
Andreas