he/him 
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
Show this thread
To build Chrome you have to run all these esoteric build tools that are obviously consequence of internal Google processes leaking.
-
-
Nah, you have to understand what repo then it makes a lot of sense
-
What do you mean?
- 1 more reply
New conversation -
-
-
Hi! Owner of that tools repo here :) you're mostly right (sorry!) but slightly off the mark on a few points. 1/
-
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/
- 2 more replies
New conversation -
-
-
The funny thing is that this is not true. At least not in the way you think it is.
-
Curious to learn more. I'm drawing from personal experiences doing open source at FB. Lots of tooling to make open source and internal work.
- 4 more replies
New conversation -
-
-
I don't think that's correct; these tools are shared by Chrome/V8 (maybe Skia too?) but do not resemble any internal Google stuff.
-
chromium is bigger and more complicated that just blink -- the tools make it so that you can compile the right UI in like less than 4 days
- 3 more replies
New conversation -
-
-
It's not as bad as how we infected the JS community with
@providesModule
(seems to be mitigated now)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Steps for installing the RN FBSDK in a RN app: ???
-
I jest though. Your work is instrumental to mine and I appreciate it. Hope to meet you, one day, and buy you a nice beverage...
End of conversation
New conversation -
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.