3 ms·
1 & 3. You are supposed to ship the waf script with the code. It's 100kb so it's not a huge burden to check it into your repo. I'm very sure it is explained in
by bjourne 10y ago
1 & 3. You are supposed to ship the waf script with the code. It's 100kb so it's not a huge burden to check it into your repo. I'm very sure it is explained in the waf book: https://waf.io/book/ https://waf.io/book/
2. Either run "chmod +x waf ./waf build" or "python waf build" Adding directories to $PATH isn't necessary.
4. I think the use case for configuring and building with the same tool is very compelling. Like:
def configure(ctx):
ctx.check_cfg(package='gtk+-2.0',
args='--cflags --libs',
uselib_store = 'GTK-2.0')
def build(ctx):
ctx.program(source = 'blah.c',
target = 'blah',
use = 'GTK-2.0')
This will add a configure check using pkg-config ensuring that gtk+ is installed. Then due to the use declaration in the call to the program() method, the correct compile and link flags will be added.
Because it is all in one tool, it is very easy. Other build systems complicates it by keeping configure and build separate.
5. True, but I prefer more power over less.
6. Tomas Nagy published some benchmarks here: http://www.freehackers.org/~tnagy/bench.txt http://www.freehackers.org/~tnagy/bench.txt Waf was 12 times faster than SCons and about 20% slower than make.