Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[5.x] Update DEFAULT_IOS_CPU for M1 arm64 simulator support #14182

Conversation

keith
Copy link
Member

@keith keith commented Oct 27, 2021

Now that bazel supports ios_sim_arm64 we can prefer this if no other iOS
CPU is passed so that developers can build the simulator builds of their
apps / tests without having to pass a flag depending on the host.

Closes #13873.

PiperOrigin-RevId: 405661296
(cherry picked from commit d7628e1)

This just missed 5.x, original PR here #13873

Now that bazel supports ios_sim_arm64 we can prefer this if no other iOS
CPU is passed so that developers can build the simulator builds of their
apps / tests without having to pass a flag depending on the host.

Closes bazelbuild#13873.

PiperOrigin-RevId: 405661296
(cherry picked from commit d7628e1)
@keith keith requested a review from lberki as a code owner October 27, 2021 22:14
@google-cla google-cla bot added the cla: yes label Oct 27, 2021
@keith
Copy link
Member Author

keith commented Oct 27, 2021

cc @Wyverald

@Wyverald Wyverald changed the base branch from master to release-5.0.0rc1 October 28, 2021 10:21
@Wyverald Wyverald merged commit ca5f67f into bazelbuild:release-5.0.0rc1 Oct 28, 2021
chiragramani pushed a commit to uber-common/bazel that referenced this pull request Feb 2, 2022
Now that bazel supports ios_sim_arm64 we can prefer this if no other iOS
CPU is passed so that developers can build the simulator builds of their
apps / tests without having to pass a flag depending on the host.

Closes bazelbuild#13873.

PiperOrigin-RevId: 405661296
(cherry picked from commit d7628e1)
@keith keith deleted the ks/update-default_ios_cpu-for-m1-arm64-simulator-support branch February 14, 2022 22:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants