Hi, On Wed, Jun 29, 2011 at 2:49 PM, Diego Biurrun <di...@biurrun.de> wrote: > On Wed, Jun 29, 2011 at 02:35:23PM -0700, Alex Converse wrote: >> 2011/6/29 Måns Rullgård <m...@mansr.com>: >> > "Ronald S. Bultje" <rsbul...@gmail.com> writes: >> > >> >> From: Frank Barchard <fbarch...@chromium.org> >> >> >> >> Signed-off-by: Ronald S. Bultje <rsbul...@gmail.com> >> >> --- >> >> cmdutils.c | 8 ++++++++ >> >> configure | 2 +- >> >> ffmpeg.c | 18 +++++++++++++++++- >> >> 3 files changed, 26 insertions(+), 2 deletions(-) >> > >> > I question the utility of this. >> >> As someone who routinely builds ffmpeg for audio-only purposes I find >> this useful. > > Why? Are you concerned about size? Extra library dependencies? > > Note that this is an honest question - I'm not trying to troll you.
It's a great way to test ffmpeg-the-tool for projects that mostly only care about libavcodec/libavformat, rather than the complete beast that is libav*. Examples of such projects are Chrome, who don't care about libswscale, libavfilter, etc. It's all disabled. However, when telling me about bugs, it's nice to be able to test under ffmpeg with the same configuration used to build Chrome itself. Ronald _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
