Re: [reSIProcate] "opt" builds

[Byron Campen <bcampen@xxxxxxxxxxxx>]

	I'm not sure why this is. I imagine this was done before we had a  
gopt build, or maybe someone wanted to release testing binaries for a  
product based on resip (no symbols, but leave the asserts in).

	Does anyone object to uncommenting these flags? Should we try for a  
more flexible approach (another configure option)?

Best regards,
Byron Campen

> I am running into this same issue. Is there a specific reason the  
> asserts
> are not compiled out in OPT build?
>
> Thanks,
>
> David
>
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf  
> Of Sunitha
> Beeram
> Sent: Wednesday, September 12, 2007 2:31 PM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] "opt" builds
>
> Hi,
>
>   We have been running resiprocate built in the opt mode
> and have run into crashes caused by some assertions. I
> was expecting that assertions will be turned off in
> non-debug modes. The makefile has explicitly commented
> out the NDEBUG flag in the opt mode :
>
> Makefile.osarch:
>         ifeq ($(VOCAL_COMPILE_TYPE),opt)
>         CXXFLAGS += $(OPTFLAGS) #-DNDEBUG
>         CFLAGS += $(OPTFLAGS) #-DNDEBUG
>         Endif
>
>
> I was wondering if I could enable these back for the opt
> mode. Should I use other modes to compile resiprocate so
> it can be used in 'releases'?
>
> Thanks,
> Sunitha.
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

Attachment: smime.p7s
Description: S/MIME cryptographic signature