[FFmpeg-devel] [PATCH] Coremake support

Måns Rullgård mans
Mon May 14 19:56:24 CEST 2007

"Ronald S. Bultje" <rbultje at ronald.bitfreak.net> writes:

> 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).

And takes autoconf command line arguments.  I have some issues with
how autoconf handles arguments so that will never happen as long as
I'm in charge of it.

> 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?

3311 lines.  How big are your final configure and Makefiles?  That's
what really matters.

M?ns Rullg?rd
mans at mansr.com

More information about the ffmpeg-devel mailing list