Sounds more familiar to unix users used to config.h
GYP and WAF need to live in parallel for some time.
Too much instability right now. Hopefully we can revisit autoconf soon.
Some people were reporting waf erroring with thread.error: can't start new thread this seems to fix that problem.
This way there won't be strange tools/.waf-12343 directories hanging about. All that waf needs to run is inside the tools/wafadmin directory.
This reverts commit 412b463.
Made a few other little corrections too.
To use the benchmarks: node benchmarks/run.js or: make benchmark The numbers reported are the elapsed milliseconds the script took to complete. Currently only benching HTTP code and timers.