[reSIProcate] removal of NDEBUG for opt (commit 3344) - an accident?

[Scott Godin]

Sorry for the late response.
Here is some old postings on this subject:
<http://list.resiprocate.org/archive/resiprocate-users/msg00603.html>
http://list.resiprocate.org/archive/resiprocate-users/msg00603.html
http://list.resiprocate.org/archive/resiprocate-devel/msg06195.html
http://list.resiprocate.org/archive/resiprocate-devel/msg06191.html

I think it would be a good idea to add a configure option in order to
compile with the NDEBUG compiler flag, or just put the NDEBUG flag back in
for opt builds.  I've been using the Stack on windows with asserts disabled
for a while now.

Scott

On Thu, May 7, 2009 at 8:50 AM, Viktor Ivanov <viktor.ivanov at securax.org>wrote:

> Hey all
>
> Is the removal of the NDEBUG define for opt an accident or is it somehow
> connected to the USE_SSL fixes from commit 3344?
>
> Currently opt builds have working asserts which might not be desired. Is it
> ok to return the define? The visual studio projects have it enabled for the
> release builds on windows.
>
>
> Best regards
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20090519/e3b8e1c2/attachment.htm>