I wonder if the end goal is to use Bazel for Chromium and Siso is an incremental step to get there
edit: asked and answered, Siso is a "drop-in" replacement for Ninja, so presumably it can read .ninja files, and so GN probably didn't need to change much to accommodate it.
This is one area where I think it makes some sense to build your own. Most projects only use a fraction of the capability of a typical build system. The last time I did this I managed the whole thing in just 300 lines of code.
I say this as a fan of Bazel.
gyp could produce ninja files. gn is short for generate ninja. Now gn produces files compatible with siso
Ninja compatible, for the flags that chromium uses. There’s some behaviour they’ve tuned for their use case.
Never heard of it, and ninja is the only way to build C++20 modules alongside CMake.
Then again, that is something that Chromium probably will never bother with.
Just Google things.