On Jun 20, 2001, Tom Tromey <[EMAIL PROTECTED]> wrote:
>>>>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Richard> With separate Makefile.am's in each directory,
Richard> automake should be able to figure the bar/foo out from
Richard> the directory paths. The user shouldn't have to worry
Richard> about what the path to the top-level is.
>>> Is this really possible? Makefile.am files may contains rules
>>> which need to be patched if you move them at another level.
Alexandre> If you're talking about the commands, I believe it's
Alexandre> relatively easy to cope with this problem: just generate,
Alexandre> in the top-level Makefile, a rule that runs the
Alexandre> corresponding rule in the sub-make.
> If that's the only approach then it might not be worth implementing.
I'm just talking about user-written rules. For automake-generated
ones, we could do the full expansion.
On second thought, thought, it's probably not too hard to prefix all
user-written rules with cd subdirectory || exit 1, taking `@' and `-'
into account. The most difficult part is probably to adjust
dependencies, in case they contain references to MAKE variables,
containing references to other MAKE variables, and so on. Especially
if they contain @AC_SUBST@itutions.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
