They've added a dependency on Go with the addition of siso.
How so? you don't need the go build toolchain installed to use Go binaries.
If I'm going to compile Chromium from source, I probably want to compile the build system from source.
Chromium Switching from Ninja to Siso
11–20 of 73 posts
Re: Chromium Switching from Ninja to Siso
#12They've added a dependency on Go with the addition of siso.
Is this consequential for a project the size of chromium?
Re: Chromium Switching from Ninja to Siso
#13Earlier quoted context omitted.
How so? you don't need the go build toolchain installed to use Go binaries.
If I'm going to compile Chromium from source, I probably want to compile the build system from source.
Why? Would you compile the compiler from source as well? From what? You need to compile the compiler's compiler from source as well, right? Where does it stop? And why is that location more valid of a decision than the one that doesn't require building the build system from source?
Re: Chromium Switching from Ninja to Siso
#14Re: Chromium Switching from Ninja to Siso
#15Looks like the Google developer in the discussion is clueless.
Re: Chromium Switching from Ninja to Siso
#16Is there an explanation what siso provides that ninja does not?
It’s new
Re: Chromium Switching from Ninja to Siso
#17Earlier quoted context omitted.
If I'm going to compile Chromium from source, I probably want to compile the build system from source.
Why? Would you compile the compiler from source as well? From what? You need to compile the compiler's compiler from source as well, right? Where does it stop? And why is that location more valid of a decision than the one that doesn't require building the build system from source?
Same can be extended for other tools that are generally used in builds like make. I never heard someone say that they need to build make from source so they can build X, unless of course you're using something like Linux From Scratch.
Re: Chromium Switching from Ninja to Siso
#18Kinda 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.
Even so, a build system migration of any kind being anything other than Bazel given the design goals of Bazel and the heritage of Chrome is an implicit indictment of Bazel itself.
I say this as a fan of Bazel.
Re: Chromium Switching from Ninja to Siso
#19Re: Chromium Switching from Ninja to Siso
#20If Siso is a drop-in alternative to Ninja, are there builds of Siso usable for building Ninja-projects, in general?