News for hackers. Stuff that matters.
Re:Benchmarks of various C++ build tools by mianos on Friday January 01, 2016 @02:23AM (#10821339)
Nice to see that WAF, being python is competitive. It goes to show that smart can beat brawn.
Re:Benchmarks of various C++ build tools by kodr on Friday January 01, 2016 @04:28AM (#10821485)
Agreed, but it seems those benchmarks were made to promote wonderbuild. I'm not sure if it's still updated (it doesn't seem so), and it uses old versions for cmake and waf.

it would also be nice to compare other build system like ninja+meson.

Re:Benchmarks of various C++ build tools by berkut on Friday January 01, 2016 @04:27AM (#10821482)
It's only really SCons which gives Python as a build system a bad name in terms of speed in my experience.
Re:Benchmarks of various C++ build tools by waterhouse on Friday January 01, 2016 @04:43AM (#10821503)
And judging by the "number of system calls" section, SCons's performance problems don't appear to be due to the Python runtime.
Re:Benchmarks of various C++ build tools by bjohan on Saturday January 02, 2016 @12:29AM (#10825209)
I'd say Python's runtime only has a small fixed startup cost that prevent it from beating natively-compiled tools in no-op rebuilds (when no source file has changed). Some tools like tup or ninja reach insanely low times that are below the startup time of Python itself. But at such low times, it doesn't matter anymore whether it's 10ms or 100ms.