Commit 1074f6f5 authored by Mark Mentovai's avatar Mark Mentovai Committed by Commit Bot

mac/arm64: Update project status document

Change-Id: Id0c9619dc31cd2e2bcb510d03baebe6f27e6c03c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364013
Commit-Queue: Nico Weber <thakis@chromium.org>
Auto-Submit: Mark Mentovai <mark@chromium.org>
Reviewed-by: default avatarNico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799674}
parent 774175b2
...@@ -11,14 +11,20 @@ We're currently bringing up the build. At the moment, everything compiles ...@@ -11,14 +11,20 @@ We're currently bringing up the build. At the moment, everything compiles
in a vanilla release build (we haven't tried anything else) and Chromium in a vanilla release build (we haven't tried anything else) and Chromium
starts up fine and seems to work. We haven't tried running tests yet. starts up fine and seems to work. We haven't tried running tests yet.
You can follow the [tracking bug](https://crbug.com/1098899) to get updates on You can follow the [Mac-ARM64 label](https://crbug.com/?q=label%3Amac-arm64) to
progress. get updates on progress.
There's a [bot](https://ci.chromium.org/p/chromium/builders/ci/mac-arm64) that There's a [bot](https://ci.chromium.org/p/chromium/builders/ci/mac-arm64-rel)
builds for arm that you can look at to get an idea of the current state. It that builds for arm that you can look at to get an idea of the current state. It
cross-builds on an Intel machine, and we don't have enough hardware to cross-builds on an Intel machine, and we don't have enough hardware to
continuously run tests. continuously run tests.
As an alternative to building locally, changes can be submitted to the opt-in
[mac-arm64-rel
trybot](https://ci.chromium.org/p/chromium/builders/try/mac-arm64-rel). A small
number of [swarming bots](https://goto.corp.google.com/run-on-dtk) are also
available for Googlers to run tests on.
To build for arm64, you have to do 2 things: To build for arm64, you have to do 2 things:
1. use the `MacOSX11.0.sdk` that comes with 1. use the `MacOSX11.0.sdk` that comes with
...@@ -28,8 +34,10 @@ To build for arm64, you have to do 2 things: ...@@ -28,8 +34,10 @@ To build for arm64, you have to do 2 things:
"custom_vars": { "mac_xcode_version": "xcode_12_beta" }, "custom_vars": { "mac_xcode_version": "xcode_12_beta" },
Then just `gclient sync` and you'll automatically get that SDK and will build Then just `gclient sync` and you'll automatically get that SDK and will build
against it. Else, manually download and install Xcode 12 for macOS Universal with it.
Apps Beta 2 and make it the active xcode with `xcode-select`.
Otherwise, manually download and install the current Xcode 12 beta and make
it the active Xcode with `xcode-select`.
2. Add `target_cpu = "arm64"` to your `args.gn`. 2. Add `target_cpu = "arm64"` to your `args.gn`.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment