[FFmpeg-devel] [PATCH] Coremake support

Ronald S. Bultje rbultje
Mon May 14 19:47:52 CEST 2007

Hi Reimar,

On May 14, 2007, Reimar Duffinger wrote:
> I think you misunderstood at least partially. The currently problem is
> setting the whole ENABLED_*, CONFIG_*, HAVE_* and TARGET_*. Some of
> these can probably be mapped to autoconf default stuff, but for
> everything else you'd still have to write code to set them.

Well, so if you call AC_CONFIG_SUBDIRS, basically your configure  
calls the ffmpeg configure, so ffmpeg's configure just does that for  
you like it always does. Essentially (this is purely theoretical),  
ffmpeg doesn't even need to be autotools-based (oh god I can see the  
replies on this one coming) _as long as it implements all the  
relevant make targets_ (distcheck being the most important one for  
me). Like I said, I'm totally fine with adding all these make targets  
to ffmpeg's build system manually, as long as it works (right now it  
doesn't). IMHO it's just a lot easier to let it all be done  
automatically by using auto* than doing it all manually. A quick wc - 
l/-c shows that my Makefile.ams + configure.ac are currently +/- 2250  
lines or 48000 bytes - how much is ffmpeg's configure + Makefile?

Anway, as per your question, you're using ffmpeg's configure, so  
specifying custom arguments to ffmpeg's configure from your configure  
(which calls ffmpeg's configure via the AC_CONFIG_SUBDIRS) can be  
done, of course (e.g. in my projects, I always build with --disable- 
ffserver, --disable-oss/sunaudio/etc., --disable-v4l, etc., b/c I  
really just need lav[fcu]) and custom build vars (--prefix, -- 
builddir, etc.) are forwarded automatically.

Or did I misunderstand you?


More information about the ffmpeg-devel mailing list