Note: Upstreaming of iOS code is still in progress, and a substantial amount of code (especially in chrome/) is not yet built. 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, these instructions are not likely to be interesting at this point.
In the directory where you are going to check out the code, create a file called
Also, you should install API keys.
Check out the code using either the new git workflow or svn method (do not use the tarball), following the iOS specific instructions. For either one, after you run
Build the target you are interested in. Since Xcode 4 has difficulty opening Chromium projects, you may want to use xcodebuild. Example command lines, depending on the target, device, and configuration you want to build:
You should always be able to build all:All, since targets are added there for iOS only after they compile.
Any *_unittests target that runs on the bots (see below) should run successfully in a local build. Nothing else runs yet—see the highlighted note at the top of this page.
Check the bots periodically for updates; more targets will come on line over time.
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).
If you followed a previous version of these instructions and added a long list of