On Mon, Dec 01, 2003 at 07:52:37PM +1100, Robert Collins wrote:
> It transforms macros and paths in an included file (called
> Makefile.rules for now) , to make them suitable for a non-recursive
> build.
> 
> As show by the test cases, this allows a couple of neat things:
> 1) A stub Makefile.am 
> ===
> include \$(srcdir)/Makefile.rules
> ===
> is all that is needed in a given subdirectory to generate a full
> makefile. (Useful if you want to be able to cd to a given dir and
> perform builds just in that dir).
> 
> 2) File paths, and canonical macro names are conveniently short - just
> what Bob F has been (rightfully IMO) complaining about.
> 
> 3) You don't end up with a huge Makefile.am to support, rather each part
> of the project has a small rules file.

At the first sight this looks exactly the same scheme I was always
longing for.  Is there any reason why this code couldn't be included
in the mainstream automake (in the 1.9 direction)?

Jirka



Reply via email to