[FFmpeg-devel] [PATCH] Coremake support

Måns Rullgård mans
Mon May 14 21:24:48 CEST 2007

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

> Hi,
> On May 14, 2007, Mans Rullgard wrote:
>> "Ronald S. Bultje" <rbultje at ronald.bitfreak.net> writes:
>>> 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.
> Probably around a trillion or so. Why is this what matters? You don't  
> maintain it and it's not part of your final lav[cfu] binary. Like  

A few reasons:

- It is what you have to sift through when it fucks up, as it inevitably

- It is what is actually run when people build the package.  The
  FFmpeg configure script runs in a few seconds flat.  Show me an
  equivalent autoconf script that runs at even half that speed.  Same
  goes for makefiles.  Despite what the automake authors may believe,
  the make program actually takes a little time to parse each line.
  Multiply a little by zillions and you'll find yourself with quite a

- It is what gets distributed in the tarball, increasing the download
  size tenfold.

> Since you appear very negative towards this, let's be constructive  
> again, how do you suggest to keep it easy (as in a one-click action)  
> to integrate ffmpeg svn revisions into a foreign source tree for  
> development purposes?

That naturally depends on what build system they use.

M?ns Rullg?rd
mans at mansr.com

More information about the ffmpeg-devel mailing list