[asterisk-dev] [non]optimized builds

[Russell Bryant]

Michiel van Baak wrote:
> On 08:56, Wed 06 Feb 08, Atis Lezdins wrote:
>> Me too, and i actually keep DONT_OPTIMIZE enabled on production.
>> Having optimization could be useful for some embedded devices, but
>> generally people would want to know - if there's a crash - then why
>> it's happening.
> 
> Same here.
> I only disable (do not enable) DONT_OPTIMIZE on soekris
> installs. most installs on server hardware run with
> DONT_OPTIMIZE enabled.

But you guys are active in the development community.  The other 99.9%
of the people that use Asterisk want it to perform as best it can (_with_
optimizations) by default.  If it crashes for them, the debugging is to see if
they can change what they are doing so it doesn't crash anymore, or find another
version that doesn't crash.

It's a vast minority that is going to go as far as to submit backtraces and help
get problems fixed.  Besides, it's trivial to make DONT_OPTIMIZE the default on
_your_ system.

# echo "MENUSELECT_CFLAGS=DONT_OPTIMIZE" > /etc/asterisk.makeopts

-- 
Russell Bryant
Senior Software Engineer
Open Source Team Lead
Digium, Inc.