waf -v clutter

[Eric S. Raymond]

Hal Murray <hmurray at megapathdsl.net>:
> devel at ntpsec.org said:
> > waf doesn't know that config.h exists; this is its way to pass configuration
> > switches.  The fact that we generate a config.h is really legacy behavior
> > from autoconf and could be eliminated, but it's low on my priority list. 
> 
> It may be "legacy", but I like it.  It's a handy chunk of documentation.

Yeah, there's something to that.  It's why looking into removing it is near the
bottom of my priority list asnd might never happen at all.

> How do waf geeks keep track of what they built?  What file do they grep when 
> they are trying to see where a suspicious symbol comes from?

I think that's what waf -v is supposed to be for.  That and eyeballing the
waf recipe files.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.