This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Make includes (was Re: Time to update documenatiopn regarding supported make implementations?)
> And the benefit is that you rarely need to maintain any explicit
> dependencies.
Except that every other module uses an autodepend tool to update the
dependencies, rather than relying on nonportable extensions.
I understand the benefit of automatic dependencies; I use them myself
on other projects (and get burned by them occasionally anyway). But
it doesn't seem right that one Makefile out of the whole GCC project
has the right to change the rules for everyone by doing something
different. Everyone else is going through the effort of making the
build work with any portable make, and the java Makefile throws that
effort away by making non-gnu makes break.