4 ms·
Last time I tried to build Chrome/Chromium I had to mess about with this build system called Ninja. (Which worked well it was just awkward to set up on Windows)
by tomc1985 9y ago
Last time I tried to build Chrome/Chromium I had to mess about with this build system called Ninja. (Which worked well it was just awkward to set up on Windows). Is that still in play?
- mastax 9y agoYes, ninja is still used.
- xyzzyz 9y agoNinja is used because it's simple, multiplatform and very fast. The mainstream alternatives offer at most 2 out of 3.
- cjhopman 9y ago"it's simple": yep, so much so that you inevitably need a meta-build system. In the context of Chrome, the build system only offers 2 out of 3.
- bigcheesegs 9y agoIt's by design that you need a meta-build system. Ninja build files were not designed to be written by hand, not even ninja itself has hand written ninja files.
- cjhopman 9y agoYes, I understand that it's designed that way. My point was that, in the context of Chrome using ninja, the claim that "Ninja is used because it's simple, multiplatform and very fast. The mainstream alternatives offer at most 2 out of 3." is a bit odd considering that the decision doesn't seem to be ninja vs mainstream alternatives but rather ninja+gn(or gyp or whatever else) vs alternatives.
- evmar 9y agoCan you elaborate on the difficulty on Windows? If you go to the home page there is a section "Getting Ninja" that links to a page with a zip file... ?
- tomc1985 9y agoIt was too long ago for me to remember specifics. Once ninja was up and running the build process was pleasant.