Not GP, I am a Gentoo user that compiles ungoogled-chromium from source. I have a 16-core AMD CPU.
Despite that, it takes 4-8 hours to compile, due to two factors: 40,000+ separate targets, of which most are C++ files (famously slow to compile anyway).
And yes, 40,000+ separate targets is no exaggeration; ninja's first run claims about 18,000 targets, and after it finishes those, it generates a second ninja file that has to compile 23,000 targets.
I personally think it's worth it. Others may disagree, and I can't blame them. I have to run it overnight.
The fact that it takes 1.5 hours on essentially an early 2000s supercomputer cluster full steam ahead to compile a fancy HTML viewer with integrated lightweight Java-like mini script language is bonkers.
Do you have to do the make clean all, or equivalent, every time? Chrome has a ton of bits and bobs built in, right? Not all of which need to be updated every time (I guess?).
I wonder how it compares to the build time of something with equivalent functionality, like firefox.
It typically takes more than 20 hours on my dual core laptop. It's a pain, but once compiled I get the best of both worlds: fast as chrome, privacy friendly as firefox.
EDIT: Looks like popularity is on the rise [1]. Hopefully it will make it into the community repository.
Despite that, it takes 4-8 hours to compile, due to two factors: 40,000+ separate targets, of which most are C++ files (famously slow to compile anyway).
And yes, 40,000+ separate targets is no exaggeration; ninja's first run claims about 18,000 targets, and after it finishes those, it generates a second ninja file that has to compile 23,000 targets.
I personally think it's worth it. Others may disagree, and I can't blame them. I have to run it overnight.