QT_NO_DEBUG, Q_ASSERT(), and release build types

[Alex Merry]

On Sunday 11 January 2009 22:34:40 Andreas Hartmetz wrote:
> 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, then the debug symbols are stripped and packaged
> separately.

It certainly doesn't seem to make sense to have QT_NO_DEBUG enabled for 
RELEASE but not for RELWITHDEBINFO.  After all, isn't the point of 
RELWITHDEBINFO to get the performance improvements of QT_NO_DEBUG (and similar 
macros) without losing the symbols useful for gdb?

Alex


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090111/97f68a0e/attachment.sig>