For Developers‎ > ‎How-Tos‎ > ‎

Build Instructions (iOS)

Note: Upstreaming of iOS code is still a work in progress, and is proceeding in conjunction with the layered components refactoring. In particular, note that it is not currently possible to build the actual browser binary, only unit tests and libraries. Unless you are actively working on upstreaming iOS code into the Chromium repository, or are working on making a layered component that supports iOS, these instructions are not likely to be interesting at this point.


  • A Mac with a version of OS X capable of running the latest version of Xcode.
  • The latest version of XCode, including the current iOS SDK.
  • The current version of the JDK (required for the closure compiler).
  • Install depot_tools.

Setting Up

In the directory where you are going to check out the code, create a chromium.gyp_env to set the build to use iOS targets (and to use hybrid builds; see Building below):

echo "{ 'GYP_DEFINES': 'OS=ios', 'GYP_GENERATORS': 'ninja,xcode-ninja', }" > chromium.gyp_env

If you aren't set up to sign iOS build products via a developer account, you should instead use:

echo "{ 'GYP_DEFINES': 'OS=ios chromium_ios_signing=0', 'GYP_GENERATORS': 'ninja,xcode-ninja', }" > chromium.gyp_env

Also, you should install API keys.

Getting the Code

Next, check out the code, with

fetch ios


Build the target you are interested in. The instructions above select the ninja/Xcode hybrid mode, which uses ninja to do the actual build, but provides a wrapper Xcode project that can be used to build targets and navigate the source. (The Xcode project just shells out to ninja to do the builds, so you can't actually inspect/change target-level settings from within Xcode; this mode avoids generating a large tree of Xcode projects, which leads to performance issues in Xcode). To build with ninja (simulator and device, respectively):

ninja -C out/Debug-iphonesimulator All
ninja -C out/Debug-iphoneos All

To build with Xcode, open build/, and choose the target you want to build.

You should always be able to build all:All, since targets are added there for iOS only when they compile.


Any target that is built and runs on the bots (see below) should run successfully in a local build. As of the time of writing, this is only unit test targets—see the highlighted note at the top of this page.

Check the bots periodically for updates; more targets (new components) will come on line over time.

Converting an existing Mac checkout into an iOS checkout

If you want to convert your Mac checkout into an iOS checkout, you can follow the next steps:

1- Add 'target_os = [ "ios" ]' to the bottom of your chromium/.gclient file.

2- Make sure you have the following in your chromium/chromium.gyp_env file (removing the chromium_ios_signing=0 if you want to make developer-signed builds):

  "GYP_DEFINES"        : "OS=ios chromium_ios_signing=0",
  "GYP_GENERATORS"     : "ninja,xcode-ninja",

Then make sure you sync again to get all the new files like the following. At the end it will run gyp_chromium which will regenerate all the build files according to the new settings.

gclient sync


If your build fails, check the iOS columns of the Mac waterfall (the last two) to see if the bots are green. In general they should be, since failures on those bots will close the tree.