This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Automatic dependency complexity
- To: tromey at cygnus dot com
- Subject: Re: Automatic dependency complexity
- From: Jeffrey A Law <law at hurl dot cygnus dot com>
- Date: Sun, 06 Dec 1998 02:41:24 -0700
- cc: egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <871zme769q.fsf@cygnus.com>you write:
> I'd like to propose changing gcc's interface to dependency tracking so
> that automake can use it more naturally. At the same time, changing
> the GNU make docs to recommend this (IMNSHO) better way of computing
> dependencies would be a good idea. Here are the new options I'm
> thinking of:
>
> -MT NAME Set name of target in generated file
> Default is computed as it is now
>
> -MF NAME Set name of `.d' file. (Default is as now.)
>
> -MH Add a fake dependency for each header file
>
> Implementation-wise, I think the code that actually generates the `.d'
> file should be extracted from cpp and put into its own file. That
> would let the java front end use the same code (right now some of it
> is duplicated).
>
>
> What do people think of this? It's on my list of stuff I want to
> implement eventually, but of course it's hard to say when I'll get to
> it.
Seems reasonable to me. The -MH stuff is a little gross, but I don't see
a good way around that problem.
jeff