Re: automake & autoconf

Date view Thread view Subject view Author view

From: Godmar Back (gback@cs.utah.edu)
Date: Sat Jan 09 1999 - 16:57:10 EST


>
> > b) all the sudden subjected us to limitations that we weren't subjected before:
> > + like no files from other directories.
>
> This can be easily worked around, and it makes Kaffe more portable.
> The VPATH hacks we used were not portable, for instance.

Okay. I thought "no files from other directories" meant to exclude
file names such as "../unix-jthreads/internal.c", but you mean that
we only disallow

    VPATH+=../unix-jthreads
    internal.o: ....

I agree with taht.

>
> > + like having to use gmake for developing.
>
> I, for one, *always* use gmake; is there anything wrong with it?

It's not part of the standard installation of many OSs.
There's nothing "wrong" with it, except that its many extensions have
a tendency to seduce developers to write Makefile nobody will ever
understand. Roland McGrath works for our group here in Utah, and the
oskit mailing list is filled with questions of people asking about
the GNUmakerules etc. that we ended up with. Thanks to gmake, he's now
the only person who can maintain the Makefiles in the Fluke project.

By contrast, I like things simple. Make for dummies.

        - Godmar


Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:33 EDT