[MPlayer-dev-eng] split configure [RFC]

[Ivo]

On Monday 08 May 2006 01:13, Attila Kinali wrote:
> On Sun, 7 May 2006 23:51:44 +0200
> Ivo <ivop at euronet.nl> wrote:
> > BTW it also involves a single Makefile
> > for the whole project with sane deps etc.. like make in the rootdir
> > will rebuild libvo if one of the vo's has changed and relink mplayer.
>
> Can you elaborate this?
> Just one big Makefile in the root that contains all dependencies
> or a similar approach as i suggested a week ago?

It's one big Makefile that contains all dependencies. What would be the 
advantage of your approach as shown in your mail from the 23rd of april?

My configure framework actually consists of two parts. One part is a library 
of small, confined tests that are loaded on demand. And the other 
(optional) part allows one to define targets (multiple objects, static 
libraries, applications, etc) and automatically generate a decent Makefile 
that contains all dependencies and other targets like install, clean, 
depend, etc.

In the end, is has to be a portable and modular autoconf/make replacement 
written in plain shell script without the bloat, learning curve, version 
incompatibilities, m4 and everything else that sucks about autotools ;-)

--Ivo