[Ffmpeg-devel] The "Intermingled Mess" issue.

[Christian Iversen]

On Monday 19 September 2005 15:03, Michel Bardiaux wrote:
> Christian Iversen wrote:
> > On Monday 19 September 2005 14:44, Michel Bardiaux wrote:
> >>Diego Biurrun wrote:
> >>>On Mon, Sep 19, 2005 at 01:53:57PM +0200, Christian Iversen wrote:
> >>>>On Monday 19 September 2005 13:45, Luca Barbato wrote:
> >>>>>Christian Iversen wrote:
> >>>>>>Just my 5c, but wouldn't something like "make menuconfig" from the
> >>>>>>Linux kernel be the perfect way to configure ffmpeg? For instance,
> >>>>>>MP3_DECODER could depend on COMMON_MPEG_ROUTINES which could pull in
> >>>>>>SOME_IDCT_ROUTINE, etc. All this would happen automatically, and the
> >>>>>>user would have no problem configuring this library.
> >>>>>>
> >>>>>>This is just a loose idea, of course - any comments?
> >>>>>
> >>>>>kbuild is relatively easy to use, offers large benefits but is a bit
> >>>>>strange, but isn't as weird as autotools, scons and imake
> >>>>>
> >>>>>Given would be quite easy make the current configure output a .config
> >>>>>that kbuild can use (making the transition painless).
> >>>>
> >>>>Then what are the developers waiting for?
> >>>
> >>>Easy: your patch.
> >>>
> >>>Diego
> >>
> >>Something is not clear to me. Would kbuild be a *mandated* tool?
> >
> > Well, I'm sure someone could write a small script to translate
> > --enable-foo and --disable-bar into the corresponding HAS_XYZ defines.
> > It's not like kbuild adds a dependency on an executable :)
>
> Let me rephrase then. Does kbuild work under Mingw? Under Cygwin? On
> OSX? Solaris? IRIX? whateverBSD?

Oh, I see. Well, I'm not sure. But I think so, yes. The menu-config part is a 
pretty trivial ncurses app, and the rest is simply include files. (afaik).

-- 
Regards,
Christian Iversen