[FFmpeg-devel] [PATCH] Coremake support

Ronald S. Bultje rbultje
Mon May 14 18:07:54 CEST 2007

Hi Luca,

On May 14, 2007, Luca Barbato wrote:
> Ronald S. Bultje wrote:
>> May I be free enough to reword this as "just by mere burden of work,
>> I decided to go with basing my new build system on the ffmpeg make
>> system, but I'd really just prefer them to do it in a way that is
>> more convenient to my purposes"? Let's not talk us versus you, let's
>> talk about what we'd like to have.
> A good way to avoid that on the first stance? Namely coordinating
> "release snapshot" across distributions/concerned parties?
> lu
> PS: I'm thinking about doing a snapshot along this or the next week  
> for
> gentoo, anybody willing to jump the bandwagon?

For distribution purposes (i.e. stable versions of software), I think  
this is indeed a good idea. I think Fedora does something similar. By  
that, it's useful for certain purposes, and it addresses important  
purposes, e.g. getting security issues addressed in a single go.

However, I think it's parallel to what I'm trying to address here,  
which is more addresses to making developing of software using ffmpeg  
easier. Development will always try to use recent (ideally svn trunk)  
versions of ffmpeg. What I'd like to have is something that  
seamlessly allows me to integrate random (basically "latest") ffmpeg  
snapshots into a project without too much hassle.

The reason that I wrote the auto* patch is because it allows exactly  
that. Without any additional work in the source tree that I'm  
integrating ffmpeg into, I can wrap it with a single line in the  
projects configure.ac (check AC_CONFIG_SUBDIRS). If such a patch were  
ever to be integrated upstream it would allow literally hassle-free  
integration of ffmpeg into any project (Reimar, seriously, check  
AC_CONFIG_SUBDIRS, it does _everything_ and is made exactly to handle  
this kind of stuff). The current configure solution doesn't allow  
that, because it doesn't support integration into the parent source  
tree for things like make dist for tarball generation and stuff like  

(Please note that I'm not advocating the use of auto* here, I'm  
trying to present it as something that it allowed me to do exactly  
this, and I agree completely with Reimar that auto* is hard to read  
(but then again, so is the current configure script...). I happen to  
be reasonably failiar with auto* which allowed me to write the patch.  
I'm open for any other solution that allows this kind of hassle-free  
integration of ffmpeg into a source tree.)


More information about the ffmpeg-devel mailing list