The purpose of this binary is to provide tools for temporary Xcode installations, e.g. to build and test Chrome / Chromium on Mac OS X and iOS.
Specifically, it provides tools for creating appropriate Xcode CIPD packages and then installing them on demand on bots and developer machines.
depot_toolsThe mac_toolchain tool is available in depot_tools as a shim which automatically installs the binary on Mac OS X.
For depot_tool-independent installation (e.g. on a bot, in a recipe), the preferred method of installing this tool is through CIPD, e.g.:
$ echo 'infra/tools/mac_toolchain/${platform} latest' | cipd ensure -ensure-file - -root .
will install the mac_toolchain binary in the current directory (as specified by the -root argument).
Note, that the CIPD package currently exists only for Mac OS, and not for any other platform, since Xcode installation only makes sense on a Mac.
You can also create shim scripts to install the actual binaries automatically, and optionally pin the mac_toolchain package to a specific revision. Pinning to latest will always install the latest available revision. For inspiration, see cipd_manifest.txt in depot_tools, and the corresponding shims, e.g. vpython.
The prebuilt CIPD package is configured and built automatically for (almost) every committed revision of infra.git. It's configuration file is mac_toolchain.yaml.
Since this is a standard Go package, you can also install it by running go install in this folder. See the infra/go/README.md file for the Go setup.
mac_toolchain install -xcode-version XXXX -output-dir /path/to/root
Add -kind mac or -kind ios argument to install a package for mac or ios tasks. iOS kind has iOS SDK and default iOS runtime installed additionally. If not specified, the tool installs a mac kind. Additionally, you can use -withRuntime=False, to exclude installing runtime dmg with the Xcode. By default, the flag is True
This command will install the requested version of Xcode.app in the /path/to/root folder. Run mac_toolchain help install for more information.
Note: to access the Xcode packages, you may need to run:
cipd auth-login
or pass the appropriate -service-account-json argument to cipd ensure.
Download the Xcode zip file from your Apple's Developer account, unpack it, and point the script at the resulting Xcode.app.
mac_toolchain upload -xcode-path /path/to/Xcode.app -legacy-ios-package=True
This will split up the Xcode.app container into several CIPD packages and will upload and tag them properly. Run mac_toolchain help upload for more options.
Update: As of MacOS13+, the xcode package should be uploaded as a whole in infra_internal/ios/xcode/mac. Therefore, the -legacy-ios-package=True flag is required for all future uploads.
The upload command is meant to be run manually, and it will upload many GB of data. Be patient.
By changing CFBundleShortVersionString and ProductBuildVersion in Xcode.app/Contents/version.plist, you can customize the Xcode version in CIPD refs and tags attached to Xcode when uploading.
Update: changing the contents in Xcode.app is no longer recommended due to the new codesign check added in macOS 13. If the Xcode will be installed and run on macOS 13+, please don't change anything in Xcode.app/Contents/version.plist.
By passing in -skip-ref-tag argument, the uploaded packages will have no CIPD ref or tag attached.
Note: During a new Xcode release, there‘s usually a new iOS runtime dmg that need to upload to cipd as well. Even in the case when there’s no new iOS runtime release, you still need to run the upload-runtime-dmg command. See below section for more information.
Each Xcode package comes with a default built-in iOS runtime (e.g. Xcode 14.3 has iOS 16.4 built-in). (Update: as of Xcode 15+, it no longer comes with an iOS runtime. All runtimes need to be installed separately) However, in our build process, we usually require building and testing chrome with n to n-2 versions of iOS to ensure backward compatibility. For example, as of early 2023, we test chrome with iOS 16.4, 15.5 and 14.4.
Therefore, we need to upload additional iOS runtimes to cipd in order for swarming jobs to download and install them to Xcode in order to support testing on those additional iOS versions. NOTE: upload-runtime-dmg command needs to be run EVERYTIME with a new release of Xcode, even when a new iOS is not released. This is CRUCIAL to ensure that the iOS cipd package ref tags are up-to-date.
Runtime is currently being uploaded to cipd using dmg format. See crbug/1440179.
[iOS simulator runtime name].dmgxcrun simctl runtime add [path/to/your/runtime/dmg].dmg (Xcode might have already automatically downloaded the latest bundled runtime during first launch. If so, then you do not have to do this step).xcrun simctl runtime list -j. For example iOS 16.2 beta 2 has a build number of 20C52.Upload the disk image file to cipd by running the below command:
mac_toolchain upload-runtime-dmg -runtime-path [path to your folder that contains the dmg file] -runtime-version [iOS version] -runtime-build [runtime build] -xcode-version [xcode version]
For example:
mac_toolchain upload-runtime-dmg -runtime-path /Users/yueshe/Documents/ios16-2-runtime/ -runtime-version ios-16-2 -runtime-build 20c52 -xcode-version 14c18
Use mac_toolchain install-runtime-dmg. Please read mac_toolchain help install-runtime-dmg to learn the logic of choosing an appropriate runtime with given input combinations. An example command:
mac_toolchain install-runtime-dmg -output-dir /Users/yueshe/Documents/ios16-2-runtime/ -runtime-version ios-16-2
Sometimes there could be multiple ios-16-2 on cipd, for example multiple beta versions of a runtime, so only the latest uploaded will be downloaded. To download a specific version of ios runtime, please also specify the xcode version that's first compatible with the runtime. For example:
mac_toolchain install-runtime-dmg -output-dir /Users/yueshe/Documents/ios16-2-runtime/ -runtime-version ios-16-2 -xcode-version 14c18
Update: this solution is deprecated as of 2023, see above section for new instructions on how to work with iOS runtime for MacOS13+
mac_toolchain uploads the default iOS runtime and the rest of Xcode to different CIPD packages. It's also able to download an Xcode package without any iOS runtime bundled.
This is useful when we want to assemble an Xcode with it's core program and the only runtime needed for iOS test tasks in infra.
Runtime related features are added at around mid 2021. Design and related changes were tracked in crbug.com/1191260.
Two types of iOS runtimes are stored in CIPD path infra_internal/ios/xcode/ios_runtime, distinguished through different combinations of tags and refs:
manually_uploaded type: Uploaded with mac_toolchain upload-runtime command.
xcode_default type: Uploaded when uploading an Xcode. Packages of this type are labeled with both runtime version & Xcode version.
Use mac_toolchain install-runtime. Either or both runtime version and Xcode version are accepted as input. Please read mac_toolchain help install-runtime to learn the logic of choosing an appropriate runtime with given input combinations.
When uploading an Xcode, the runtime bundled in the Xcode version is uploaded automatically as an xcode_default package.
Use mac_toolchain upload-runtime to upload a manually_uploaded runtime package. It's recommended to only use this command on the official runtimes downloaded through Xcode to system library /Library/Developer/CoreSimulator/Profiles/Runtimes/.
Use following command to download an Xcode package without runtime
mac_toolchain install -kind ios -xcode-version SOME_VERSION -output-dir path/to/Xcode.app -with-runtime=False
This is specifically used in iOS tester machines across chromium infra where mac_toolchain is invoked to download Xcode. iOS test runner further downloads the requested runtime in task and assembles a full Xcode package with runtime from multiple packages downloaded (or read from cache).
Update (2023): in MacOS13+, all Xcode.app contents will be bundled in the “mac” package, so the above command will still install the runtime to the output directory. Update (2023 Jun): For Xcode15+, Xcode no longer bundles runtime within xcode.app, so installing runtime with this command will indeed not install the runtime.
To debug Xcode packaging locally, run:
mac_toolchain package -output-dir path/to/dir -xcode-path /path/to/Xcode.app
This will drop mac.cipd, ios.cipd (not required anymore in MacOS13+) files in path/to/out directory and will not try to upload the packages to CIPD server.
You can then install Xcode from these local packages with:
cipd pkg-deploy -root path/to/Xcode.app path/to/out/mac.cipd
To debug iOS runtime packaging locally, run:
mac_toolchain package-runtime-dmg -output-dir path/to/dir -runtime-path parent/path/to/ios-runtime-dmg/ -runtime-version [e.g. ios-16-1] -runtime-build [e.g. 20b71] -xcode-version [e.g 14b47b]
This will drop ios_runtime_dmg.cipd files in path/to/out directory and will not try to upload the packages to CIPD server.
You can then install iOS runtime from this local package with:
cipd pkg-deploy -root path/to/ios-runtime-dmg/ path/to/out/ios_runtime_dmg.cipd