On 2020/03/14 23:57:48, hanwenn wrote: > I have been experimenting with Ninja (https://ninja-build.org/), but Ninja has a > very restricted model. Make functions, wildcards, etc. are not possible. In > order to advance my experiments, I'm trying to clean up the build so I can port > more of the build over.
>From the website: "it [Ninja] is designed to have its input files generated by a higher-level build system". And that's to be taken literally, the syntax is so low-level that it's no fun to read it, let alone write. So big NACK from me for switching to Ninja. Both Meson and CMake are able to generate files for Ninja, but Meson is pretty new and I'm not sure yet whether it will become one of those projects that goes away after a few years (see Scons). CMake would certainly work, but has its own problems and corner cases. In sum we should definitely cleanup the current build system and see where it gets us. What I'm not really happy with is replacing all of this with custom Python scripts, however small they are. Skimming over scan-mf-deps.py, that looks totally doable in around half the lines with a sh script. What's the motivation to use Python for all of this? https://codereview.appspot.com/553700043/
