Diego Biurrun <[email protected]> writes:

> On Tue, Aug 14, 2012 at 11:52:54AM +0100, Måns Rullgård wrote:
>> Diego Biurrun <[email protected]> writes:
>> > On Mon, Aug 13, 2012 at 07:40:38PM +0100, Måns Rullgård wrote:
>> >> Diego Biurrun <[email protected]> writes:
>> >> 
>> >> > A new hidden config variable is added for the codecs that depend on
>> >> > the error resilience parts.
>> >> > ---
>> >> >  configure           |   43 ++++++++++++++++++++-------------------
>> >> >  libavcodec/Makefile |   55 
>> >> > ++++++++++++++++++--------------------------------
>> >> >  2 files changed, 42 insertions(+), 56 deletions(-)
>> >> 
>> >> [...]
>> >> 
>> >> > +OBJS-$(CONFIG_ERROR_RESILIENCE)        += error_resilience.o
>> >> 
>> >> For a single file, what does this gain?
>> >
>> > The same could be said for most of the parts needed by different
>> > codecs...
>> 
>> Some of those have a config symbol for other reasons.  Anyhow, if you
>> prefer it this way I don't particularly mind.
>
> We could either develop a strategy now and come up with criteria when
> to assign a config symbol or we can continue down the current,
> slightly ad-hoc, path.  Right now I'd say we assign config symbols to
> identifiable self-contained features, so I believe error resilience
> and the range coder fit the bill.

Fine, go for it.

-- 
Måns Rullgård
[email protected]
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to