Re: NDEBUG when building packages?

[Kumar Appaiah <a.kumar@alumni.iitm.ac.in>]

On Fri, Jun 07, 2013 at 11:54:49AM +0200, Mathieu Malaterre wrote:
> cmake from sid makes it even harder. RelWithDebInfo now contains
> -DNDEBUG ... I have to source-upload all my packages :(
> 
> $ grep NDEBUG ChangeLog.manual
>       Add -DNDEBUG to RelWithDebInfo flags where where Release flags had it.
> 
> 
> The solution (backward compat) is now:
> 
> Either do *not* define CMAKE_BUILD_TYPE, or define CMAKE_BUILD_TYPE to
> Debug (and hope -DNDEBUG does not creep in ever)

While we're at it, could you please let me know what is the best
practice for package builds that generate debug symbol packages?
Ideally, I would hapve to rebuild the whole package TWICE, once with
-O0 -g, and the other time with -O2, right?

Currently, I don't bother with this, since the the debug library with
-O2 is still useful, other than the odd "optimized out" messages. In
addition, I don't want to add an additional burden to the buildds for
this, since the package is probably never used on architectures other
than i386/amd64.

Thanks.

Kumar

-- 
martin@bdsi.com (no longer valid - where are you now, Martin?)
		-- from /usr/src/linux/drivers/cdrom/mcd.c