On Mon, Nov 4, 2013 at 12:53 PM, Modestas Vainius <mo...@debian.org> wrote: > Hello, > > pirmadienis 04 Lapkritis 2013 11:37:52 Mathieu Malaterre rašė: >> According to: >> >> http://bugs.debian.org/701233 >> >> "-DCMAKE_BUILD_TYPE=RelWithDebInfo" is the default in debhelper. While: >> >> http://bugs.debian.org/701231 >> >> Specifies that compilation flags should *not* contains -DNEBUG >> >> If this cannot be fixed in cmake (which would make sense), I guess it >> can be reassigned to debhelper. > > Well, I certainly won't change cmake upstream defaults for RelWithDebInfo. > However, this makes me wonder if we should "invent" a new build type which > could be used for Debian package building and switch to it in debhelper. > > Even having read the bugs and the thread you linked me to, I still don't > understand what's so evil about NDEBUG...
I think the idea is that assert() is mostly for debugging purpose but should not be used in production. ref: http://stackoverflow.com/a/2528386/136285 Maybe Ian has some more comments in which cases assert() is EBW. Anyway I think Debian policy should define the set of compilation flags (eg. hardening goal), so that we have -easy- reproduceable behavior. And build systems (cmake, autotools) should not defines for us which flags to use (unless of course they match debian policy). 2cts -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
