Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(201)

Side by Side Diff: docs/ios_build_instructions.md

Issue 1753693002: docs: fix markdown issues in ios_build_instructions.md (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 4 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 ### Build Instructions (iOS) 1 ### Build Instructions (iOS)
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 10
(...skipping 71 matching lines...) Expand 10 before | Expand all | Expand 10 after
82 If you want to convert your Mac checkout into an iOS checkout, you can 82 If you want to convert your Mac checkout into an iOS checkout, you can
83 follow the next steps: 83 follow the next steps:
84 84
85 1- Add 'target\_os = [ "ios" ]' to the bottom of your chromium/.gclient 85 1- Add 'target\_os = [ "ios" ]' to the bottom of your chromium/.gclient
86 file. 86 file.
87 87
88 2- Make sure you have the following in your chromium/chromium.gyp\_env 88 2- Make sure you have the following in your chromium/chromium.gyp\_env
89 file (removing the `chromium_ios_signing=0` if you want to make 89 file (removing the `chromium_ios_signing=0` if you want to make
90 developer-signed builds): 90 developer-signed builds):
91 91
92 { 92 `{
93
94 "GYP\_DEFINES" : "OS=ios chromium\_ios\_signing=0", 93 "GYP\_DEFINES" : "OS=ios chromium\_ios\_signing=0",
95
96 "GYP\_GENERATORS" : "ninja,xcode-ninja", 94 "GYP\_GENERATORS" : "ninja,xcode-ninja",
97 95 }`
98 }
99
100 \
101 96
102 Then make sure you sync again to get all the new files like the 97 Then make sure you sync again to get all the new files like the
103 following. At the end it will run gyp\_chromium which will regenerate 98 following. At the end it will run gyp\_chromium which will regenerate
104 all the build files according to the new settings. 99 all the build files according to the new settings.
105 100
106 \
tfarina 2016/03/01 12:54:52 Admittedly, I didn't know what to do (how to fix)
107
108 `gclient sync` 101 `gclient sync`
109 102
110 \
111
112 Troubleshooting 103 Troubleshooting
113 --------------- 104 ---------------
114 105
115 If your build fails, check the iOS columns of [the Mac 106 If your build fails, check the iOS columns of [the Mac
116 waterfall](http://build.chromium.org/p/chromium.mac/console) (the last 107 waterfall](http://build.chromium.org/p/chromium.mac/console) (the last
117 two) to see if the bots are green. In general they should be, since 108 two) to see if the bots are green. In general they should be, since
118 failures on those bots will close the tree. 109 failures on those bots will close the tree.
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698