Re:GNU make insanity: finding the value of the -j parameter
by MereInterest on Saturday March 28, 2015 @06:23PM
(#9282972)
Out of curiosity, what are the quagmire-ish aspects of scons? I've been using it for a while, and it hasn't seemed too bad, which probably means that I haven't run into them yet.
[ Parent
| on HN ]
Re:GNU make insanity: finding the value of the -j parameter
by michael_h on Saturday March 28, 2015 @08:40PM
(#9283406)
Scons itself isn't bad, but it's power is also it's downfall: the build script is an unrestricted Python file. I almost always find that something 'clever' has been stashed in the SConscript. Plus, everybody writes wrapper functions for the env.* stuff - meaning just about every project has a second, hidden codebase that you need to learn first.
Re:GNU make insanity: finding the value of the -j parameter
by MereInterest on Saturday March 28, 2015 @09:27PM
(#9283535)
Ah, got it. I'll admit that I tend to make build scripts that are a bit too complicated, due to the freedom of having a full language, but it is quite nice to have when needed. It does end up with build scripts that are far more flexible, though, not having read build scripts that others have written, I don't know how much of a cost there is to it.