I'm using Fedora 16 and I've successfully compiled Chromium from source (the first time I compiled something from source) a while back following these instructions:


At the end of the process, everything worked. However, after multiple attempts, I have had no luck in compiling a newer version of the program. I am stuck with Version 20.0.1100.0 custom (132047). Before re-building, I follow the steps to syncing my sources. But after all of the steps, build 132047 is still what I have.

Can someone help me please to building newer builds and using them as I can't seem to find anything on the internet.


  • When you update the source, do you see what version your snapshot is at? – Mat May 28 '12 at 15:50
  • @Mat yes, it shows a newer version (higher number) of the snapshot. – Jeremy Rea May 28 '12 at 15:55
  • Are you certain you're running your newly-compiled executable(s)? (Make sure you don't have any "old" chrome windows open.) – Mat May 28 '12 at 15:56
  • I would think so. I closed chromium, and deleted my old output folder for the build. Once I finished building, I would run chromium from the new executable but the build version remains that of the previous one instead of the newer one. – Jeremy Rea May 28 '12 at 19:26
  • 1
    This is how the Arch package builds the development version from source. Seems pretty complicated, but it might be useful. – Sparhawk Feb 22 '15 at 20:38

Inspired by this thread try the following


VM with 4GB Memory + 40GB harddrive


 1. mkdir -pv ~/chromium
 2. cd ~/chromium
 3. git config --global user.name "You Name"
 4. git config --global user.email “youremail@example.com”
 5. git config --global core.autocrlf false
 6. git config --global core.filemode false
 7. git config --global color.ui true
 8. git clone https://chromium.googlesource.com/chromium/tools/depot_tools
 9. export PATH=$PATH:~/chromium/depot_tools See Update Notes 1
10. mkdir -v ~/chromium/buildhost 
11. cd ../buildhost 
12. fetch --nohooks chromium
13. cd src && ./build/install-build-deps.sh
14. gclient sync (this also does runhooks)
15. gclient runhooks 
16. ninja -C out/Release chrome

I have found that having 4GB memory and a large disk was important. The chromium project is ~15GB and the builds out/Release will be ~2GB and out/Debug >8GB

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.