2 ms·
> Yeah I think we're in agreement, except that Ninja is not a replacement for Make. I would definitely disagree with this. Make's higher-level logic/graph desc
by klodolph 8y ago
> Yeah I think we're in agreement, except that Ninja is not a replacement for Make.
I would definitely disagree with this. Make's higher-level logic/graph description features are only incidental, as Ninja proved, you can remove those features and end up with a tool that is equally valuable, more or less. To abuse an analogy, if I'm shopping for notebooks, I don't need to buy a notebook and pen shrink-wrapped together. I already have plenty of pens.
You're right that Bazel isn't good for open-source projects with diverse dependencies, but I think this is a problem that can be solved by developing some more infrastructure for that and writing the appropriate Starlark code (to be called from your your WORKSPACE file and create the appropriate repositories somehow). That code just isn't around yet.
- chubot 8y agoAll I'm saying is that Make was designed to be hand-written and often is, and Ninja was designed to be generated, and almost always is. See the manual: https://ninja-build.org/manual.html#_philosophical_overview https://ninja-build.org/manual.html#_philosophical_overview Concretely, if you look at how Android or buildroot used GNU make, you can't do that with Ninja alone -- you need another tool. GNU make is Turing complete, and Ninja isn't. IMO the Ninja design is better (which isn't surprising since it's not an accretion over decades).