QT_NO_DEBUG, Q_ASSERT(), and release build types

[Armin Berres]

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_messages_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.

Is it understandable what I mean? Otherwise I'll try again... ;-)

Greetings,
Armin