Live data from Hacker News

Chromium Switching from Ninja to Siso

groups.google.com

1–10 of 73 posts

Re: Chromium Switching from Ninja to Siso

#3
I wonder if AOSP will also move over to Siso. Since it is advertised as a drop in replacement it would take less resources than the Bazel migration which got canceled. The readme explicitly calls out a feature used by AOSP, so it is plausible that thought was put into it.

Re: Chromium Switching from Ninja to Siso

#8

Kinda impressive and terrifying that Chromium needs its own build system. Kinda strange that Bazel was right there, also from Google, and they not only choose not to use it, but also reference it in the name of the new tool.

If Android was anything to go by, migrating build systems is a risky endeavour. Miso claims compatibility with ninja, so I’m guessing this route was deemed easier to make incremental improvements.

Re: Chromium Switching from Ninja to Siso

#9

Kinda impressive and terrifying that Chromium needs its own build system. Kinda strange that Bazel was right there, also from Google, and they not only choose not to use it, but also reference it in the name of the new tool.

To be fair, Bazel didn't exist when Chrome started.
Post reply on HN