Chromium Code Reviews| OLD | NEW |
|---|---|
| 1 # iOS Build Instructions | 1 # iOS Build Instructions |
| 2 | 2 |
| 3 **Note:** Upstreaming of iOS code is still a work in progress. In particular, | 3 **Note:** Upstreaming of iOS code is still a work in progress. In particular, |
| 4 note that **it is not currently possible to build an actual Chromium app.** | 4 note that **it is not currently possible to build an actual Chromium app.** |
| 5 Currently, the buildable binaries are ios\_web\_shell (a minimal wrapper around | 5 Currently, the buildable binaries are ios\_web\_shell (a minimal wrapper around |
| 6 the web layer), and various unit tests. | 6 the web layer), and various unit tests. |
| 7 | 7 |
| 8 ## Prerequisites | 8 ## Prerequisites |
| 9 | 9 |
| 10 * A Mac with a version of OS X capable of running the latest version | 10 * A Mac with a version of OS X capable of running the latest version |
| (...skipping 74 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 85 | 85 |
| 86 To run in the simulator from the command line, you can use `iossim`. For | 86 To run in the simulator from the command line, you can use `iossim`. For |
| 87 example, to run a debug build of ios\_web\_shell: | 87 example, to run a debug build of ios\_web\_shell: |
| 88 | 88 |
| 89 ```shell | 89 ```shell |
| 90 out/Debug-iphonesimulator/iossim out/Debug-iphonesimulator/ios_web_shell.app | 90 out/Debug-iphonesimulator/iossim out/Debug-iphonesimulator/ios_web_shell.app |
| 91 ``` | 91 ``` |
| 92 | 92 |
| 93 ## Converting an existing Mac checkout into an iOS checkout | 93 ## Converting an existing Mac checkout into an iOS checkout |
| 94 | 94 |
| 95 If you want to convert your Mac checkout into an iOS checkout, you can | 95 If you want to convert your Mac checkout into an iOS checkout, follow the steps |
| 96 follow those steps: | 96 below: |
| 97 | 97 |
| 98 1. Add `target_os = [ "ios" ]` to the bottom of your `chromium/.gclient` | 98 1. Add `target_os = [ "ios" ]` to the bottom of your `chromium/.gclient` |
|
sdefresne
2016/03/04 18:09:51
nit: like bulleted list, this need to be indented
tfarina
2016/03/04 18:47:57
Ah, that is very true. Thanks for noticing. Both a
| |
| 99 file. | 99 file. |
| 100 | 100 |
| 101 2. Make sure you have the following in your `chromium/chromium.gyp_env` | 101 2. Make sure you have the following in your `chromium/chromium.gyp_env` |
| 102 file (removing the `chromium_ios_signing=0` if you want to make | 102 file (removing the `chromium_ios_signing=0` if you want to make |
| 103 developer-signed builds): | 103 developer-signed builds): |
| 104 | 104 |
| 105 ```json | 105 ```json |
| 106 { | 106 { |
| 107 "GYP_DEFINES" : "OS=ios chromium_ios_signing=0", | 107 "GYP_DEFINES" : "OS=ios chromium_ios_signing=0", |
| 108 "GYP_GENERATORS" : "ninja,xcode-ninja", | 108 "GYP_GENERATORS" : "ninja,xcode-ninja", |
| 109 } | 109 } |
| 110 ``` | 110 ``` |
| 111 | 111 |
| 112 Then make sure you sync again to get all the new files like the following. At | 112 3. Make sure to sync again to fetch the iOS specific dependencies and |
| 113 the end it will run `build/gyp_chromium` which will regenerate all the build | 113 regenerate build rules using: |
| 114 files according to the new settings. | |
| 115 | 114 |
| 116 ```shell | 115 ```shell |
| 117 gclient sync | 116 gclient sync |
| 118 ``` | 117 ``` |
| 119 | 118 |
| 120 ## Troubleshooting | 119 ## Troubleshooting |
| 121 | 120 |
| 122 If your build fails, check the iOS columns of [the Mac | 121 If your build fails, check the iOS columns of [the Mac |
| 123 waterfall](http://build.chromium.org/p/chromium.mac/console) (the last | 122 waterfall](http://build.chromium.org/p/chromium.mac/console) (the last two) to |
| 124 two) to see if the bots are green. In general they should be, since | 123 see if the bots are green. In general they should be, since failures on those |
| 125 failures on those bots will close the tree. | 124 bots will close the tree. |
| OLD | NEW |