waf -v clutter

[Hal Murray]

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.

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?



-- 
These are my opinions.  I hate spam.