When comparing GNU Make vs Waf, the Slant community recommends GNU Make for most people. In the question“What are the best open-source build systems for C/C++?” GNU Make is ranked 3rd while Waf is ranked 10th. The most important reason people chose GNU Make is:
Make takes advantage of the powerful UNIX shell, using it at it's full potential. STDIN and STDOUT are especially useful because of their versatility.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Uses the full power of the UNIX shell
Make takes advantage of the powerful UNIX shell, using it at it's full potential. STDIN and STDOUT are especially useful because of their versatility.
Pro No need for wrapper modules
Other build tools need wrapper modules to do certain tasks. The biggest disadvantage of these wrapper modules is that they bind you to a version of that tool. With Make you don't have that problem, there's no need for wrappers and no tools to bind you to a version, you can use any version of Make that you want.
Pro Works with more than just node.js
Since it's written in C and can be found in all UNIX-based systems it can be used on platforms other than node.js.
Pro Written in Python
You don't have to learn a domain specific syntax. If you know Python, it's a breeze.
Pro File changes are tracked based on a hash of their changes not the time stamp
This means that switching branches in git isn't a big deal.
Pro Very fast
Much faster than its predecessor SCons.
Pro Fairly easy to extend
Pro Very simple graph based API
Cons
Con Doesn't run on Windows by default
Make requires Cygwin/msys2/MinGW to run on Windows.