Diego Biurrun <di...@biurrun.de> writes:
> On Tue, Nov 27, 2012 at 09:36:17PM +0000, Måns Rullgård wrote:
>> Diego Biurrun <di...@biurrun.de> writes:
>> > On Tue, Nov 27, 2012 at 08:57:52PM +0000, Måns Rullgård wrote:
>> >> Diego Biurrun <di...@biurrun.de> writes:
>> >> > --- a/configure
>> >> > +++ b/configure
>> >> > @@ -1956,6 +1957,10 @@ for opt do
>> >> > --disable-everything)
>> >> > map 'eval unset \${$(toupper ${v%s})_LIST}' $COMPONENT_LIST
>> >> > ;;
>> >> > + --disable-all)
>> >> > + map 'eval unset \${$(toupper ${v%s})_LIST}' $COMPONENT_LIST
>> >> > + disable $LIBRARY_LIST $PROGRAM_LIST doc network
>> >>
>> >> Why do you explicitly disable network? It is part of libavformat.
>> >
>> > It is a CONFIG_ option not part of any component group so that if you
>> > --enable-libavformat, you would start with a non-minimal libavformat
>> > configuration:
>>
>> Is there any use in having network enabled if none of the network
>> protocols are enabled?
>
> There isn't, that's why I disabled it so that a --disable-all build
> would be truly minimal.
>
> It feels as though you are asking because you have something more specific
> in mind What are you suggesting? Dropping network from the list of
> command line options and have protocols autoselect it instead?
Have protocols _select it but keep it on the command line.
--
Måns Rullgård
m...@mansr.com
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
