tech-toolchain archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: make: dealing with targets with multiple outputs



Simon J. Gerraty <sjg%juniper.net@localhost> wrote:

> matthew green <mrg%eterna.com.au@localhost> wrote:
> > AFAICT, yacc handling is currently poor and is (part of)
> 
> Yes I know, that's why I started this thread ;-)
> Since I had a thought on how to fix.
> 
> > what dholland is trying to propose a fix for.
> 
> Ideally any solution should DTRT even with suffix rules.

Oh and preferably behavior should be stable, ie if foo.h and foo.c both
generated from foo.y, then yacc should for example always be run for
foo.c even if it appears to be up-to-date but foo.h got removed.
This would help keep meta mode happy.

The syntax I was suggesting would allow for that, with I think minimal
magic.

Regardless, I suspect the internal plumbing for David's idea would be
rather similar to mine - each GNode needs a list of nodes that it is
"related" to.

In my idea, you'd always build the first node of that set
if any are out-of-date and simply mark all of them up-to-date.
This would ensure the same .meta file is always used.

If I understood David's proposal, he'd be stat()ing each of those
related targets after making any of them.

--sjg


Home | Main Index | Thread Index | Old Index