Steps to build Chrome:
1. Clone a tools repo
2. Add it to your $PATH (wtf?)
3. Clone Chrome repo
4. Setup the build
5. Compile
-
Show this thread
-
Steps to build WebKit: 1. Clone a repo 2. Run a single command
2 replies 3 retweets 28 likesShow this thread -
To build Chrome you have to run all these esoteric build tools that are obviously consequence of internal Google processes leaking.
7 replies 2 retweets 24 likesShow this thread -
Replying to @sebmck
Hi! Owner of that tools repo here :) you're mostly right (sorry!) but slightly off the mark on a few points. 1/
1 reply 0 retweets 2 likes -
Replying to @phasmantistes @sebmck
Most of the tools to build chrome (GN, ninja, goma) basically live in the chromium repo. The executables in depot_tools are mostly shims. 2/
1 reply 0 retweets 1 like -
Replying to @phasmantistes @sebmck
But depot_tools provides other stuff like git extensions and tools for interacting with code review, so that's why it is on
$path.2 replies 0 retweets 1 like
I'm worried about the names of the binaries colliding with another package. One of them is just names 'fetch' which leaves me concerned.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 