build: Waf performance regression on macOS
I have had some reasons to use a Mac this week and the performance of running even a simple program such as './waf --run sample-simulator' is dreadful. It may take 1-3 minutes to execute. Similar performance exists under ./waf shell. However, running the executable directly is fast.
Upgrading to waf-2.0.14 does not change performance.
In looking at timestamps from an output of './waf -vvv --run sample-simulator', it seems that most of the time is taken in the stage where Waf is checking hashes of every source file, and up to ten Python processes are spawned during this time. Hash checking should not take much time so it must be something else.
Edited by Tom Henderson