Comment by bgirard
1 year ago
> Chromium's codebase isn't so bad for a first timer.
Agreed
> It took me like 30 minutes
I can tell you didn't need to build it ;)
1 year ago
> Chromium's codebase isn't so bad for a first timer.
Agreed
> It took me like 30 minutes
I can tell you didn't need to build it ;)
Why build it if you are just reading? I find https://source.chromium.org/chromium wonderful. With things like go-to-definition and find-all-overridden-functions working wonderfully well.
I find this to be ideal when working with a large codebase. I don't even need an editor with fancy intelligence features and LSP integration; a bare bones vim or emacs paired with a website with all the intelligence already there.
> Why build it if you are just reading?
Is this a serious question? Assuming it is, to insert printf statement, or attach a debugger and step through the program and take backtraces to supplement or confirm the information you gather from reading the code.
Yes it's a serious question. And no, "reading" doesn't involve inserting printf statements or taking backtraces. These are different activities. That's called debugging and not reading.
The OP's scenario is being curious how Chromium does something: so it suffices to find the relevant snippet and then copy it elsewhere. The Chromium code is assumed to be already working and does not need debugging.
4 replies →