/build/config/ios/codesign.py code-sign-bundle -t=iphoneos -i=0123456789ABCDEF0123456789ABCDEF01234567 -e=././build/config/ios/ist -b=obj/ios/web/shell/ios_web_shell ios_web_shell.appĮrror: no mobile provisioning profile found for "-web-shell". Ninja : Entering directory `out/Debug-iphoneos'įAILED: ios_web_shell.app/ios_web_shell ios_web_shell.app/_CodeSignature/CodeResources ios_web_shell.app/embedded.mobileprovision
Generally, if the mobile provisioning profile is missing then the code signing step will fail and will print the bundle identifier of the bundle that could not be signed on the command line, e.g.: $ autoninja - C out / Debug - iphoneos ios_web_shell setup-gn.py creates sub-directories named out/$ and may require specific capabilities. Look at src/ios/build/tools/nfig for available configuration options.įrom this point, you can either build from Xcode or from the command line using autoninja. You can customize the build by editing the file $HOME/.setup-gn (create it if it does not exist). Xcode project is an artifact, any changes made in the project itself will be ignored.
More information about developing with Xcode.
Since the iOS build is a bit more complicated than a desktop build, we provide ios/build/tools/setup-gn.py, which will create four appropriately configured build directories under out for Release and Debug device and simulator builds, and generates an appropriate Xcode project ( out/build/all.xcodeproj) as well.
Optional: You can also install API keys if you want your build to talk to some Google services, but this is not necessary for most development and testing purposes. The remaining instructions assume you have switched to the src directory: $ cd src gclient file and a directory called src in the working directory. When fetch completes, it will have created a hidden.
If you don't want the full repo history, you can save a lot of time by adding the -no-history flag to fetch.Įxpect the command to take 30 minutes on even a fast connection, and many hours on slower ones. Run the fetch tool from depot_tools to check out the code and its dependencies. Assuming you cloned depot_tools to /path/to/depot_tools: $ export PATH = "$PATH:/path/to/depot_tools" Get the codeĬreate 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): $ mkdir chromium & cd chromium The current version of the JDK (required for the Closure compiler).Ĭlone the depot_tools repository: $ git clone https : ///chromium/tools/depot_tools.gitĪdd depot_tools to the end of your PATH (you will probably want to put this in your ~/.bashrc or ~/.zshrc).