On Thu, Apr 02, 2015 at 01:55:26PM +0200, Vittorio Giovara wrote: > On Thu, Apr 2, 2015 at 1:20 PM, Diego Biurrun <[email protected]> wrote: > >> --- a/configure > >> +++ b/configure > >> @@ -315,6 +315,8 @@ Developer options (useful when working on Libav > >> itself): > >> (group) and PROB the probability associated > >> with > >> NAME (default 0.5). > >> --random-seed=VALUE seed value for --enable/disable-random > >> + --disable-valgrind-backtrace do not print a backtrace under Valgrind > >> + (needs --disable-optimizations) > > > > I don't like this. Why not automatically enable it when optimizations > > are disabled instead? > > It is automatically enabled when optimizations are disabled, I just > added some help text because users could wonder why it's not enabled > (eg. they do need to disable optimizations).
The text is still confusing. But before fixing that I think we should consider enabling this unconditionally if optimizations are disabled. What's the point of having a disable switch for this? (We already have far too many configure parameters.) Diego _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
