Chromium supports building on Windows, Mac and Linux host systems. Linux is required for building Android, and a Mac is required for building iOS.
This page documents common checkout and build instructions. There are platform-specific pages with additional information and requirements:
Set up your environment
Check out and install the depot_tools package. This contains the custom tools necessary to check out and build.
Create a chromium directory for the checkout and change to it (you can call this whatever you like and put it wherever you like, as long as the full path has no spaces):
Check out the source code
Use the "fetch" tool that came with depot_tools:
fetch chromium # [fetch --no-history chromium]
cd src # All other commands are executed from the src/ directory.
--no-history if you don't need repo history and want a faster checkout. Expect a checkout to take at least 30 minutes on fast connections, and many hours on slower connections.
Some platform-specific pages (linked above) may have extra instructions. In particular, on Ubuntu Linux run:
Optional: install API keys which allow your build to use certain Google services. This isn't necessary for most development and testing purposes.
Run hooks to fetch everything needed for your build setup.
Update the checkout
To sync to newer versions of the code (not necessary the first time), run the following in your src/ directory:
The first command updates the primary Chromium source repository and rebases your local development branches on top of tip-of-tree. The second command updates all of the dependencies specified in the DEPS file. See also "More help managing your checkout" below.
Setting up the build
GN is our meta-build system. It reads build configuration from
BUILD.gn files and writes Ninja files to your build directory. To create a GN build directory:
gn gen out/Default
- You only have to do this once, it will regenerate automatically when you build if the build files changed.
- You can replace
out/Default with another name inside the
- To specify build parameters for GN builds, including release settings, see GN build configuration. The default will be a debug component build matching the current host operating system and CPU.
- For more info on GN, run
gn help on the command line or read the quick start guide.
Build Chromium (the "chrome" target) with Ninja using the command:
ninja -C out/Default chrome
List all GN targets by running
gn ls out/Default from the command line. To compile one, pass to Ninja the GN label with no preceding "//" (so for
ninja -C out/Default ui/display:display_unittests).
You can run chrome with (substituting "Default" with your build directory):
Run the test targets listed above in the same manner. You can specify only a certain set of tests to run using
You can find out more about GoogleTest on the GoogleTest wiki page
Quick start to submit a patch
See contributing code for a more in-depth guide.
git checkout -b my_patch
...write, compile, test...
git commit -a
git cl upload
git cl upload command will upload your code review to codereview.chromium.org for review.
- Add reviewers and submit your code for review by clicking on "Publish+Mail Comments" (you can leave the mail message empty).
- If you have try bot access, you can click "CQ dry run" which will compile and run the tests.
- Once your patch has been reviewed and marked LGTM ("Looks Good To Me") by an authorized reviewer, click the "Commit" checkbox below the patch to submit to the commit queue.
More help managing your checkout
- Ensure your checkout has been properly updated (
- Check you're on a stable, unmodified branch from master (
- Check you have no uncommitted changes (
- Join the
#chromium IRC channel on
irc.freenode.net (see the IRC page for more).
- Join the chromium-dev Google Group, and other technical discussion groups. These are not support channels for Chrome itself but forums for developers.
- If you think there is an infrastructure problem that affects many developers, file a new bug with the label 'Infra'. It will be looked at by our infrastructure team.
- If you work at Google, check out the Googler-specific Chrome documentation.