On Fri, Nov 16, 2012 at 10:34:37AM +0000, Måns Rullgård wrote: > Diego Biurrun <di...@biurrun.de> writes: > > On Fri, Nov 16, 2012 at 10:05:13AM +0000, Måns Rullgård wrote: > >> Diego Biurrun <di...@biurrun.de> writes: > >> > --- a/configure > >> > +++ b/configure > >> > @@ -980,6 +980,15 @@ COMPONENT_LIST=" > >> > > >> > +LIBRARY_LIST=" > >> > + avcodec > >> > + avdevice > >> > + avfilter > >> > + avformat > >> > + avresample > >> > + swscale > >> > +" > >> > @@ -1782,13 +1786,8 @@ host_os=$target_os_default > >> > > >> > -enable avcodec > >> > -enable avdevice > >> > -enable avfilter > >> > -enable avformat > >> > -enable avresample > >> > +enable $LIBRARY_LIST > >> > enable avutil > >> > -enable swscale > >> > >> Why is avutil not in that list? > > > > Because libavutil is a necessary part of any build and can never be > > left out. > > It still leaves the code looking odd, with all uses of $LIBRARY_LIST > followed by an explicit avutil.
Is the patch OK with avutil in that list? That would entail making avutil a normal config option as opposed to one not available on the command line, as it is currently. Diego _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
