-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Build aarch64-apple-ios-sim as part of the full macOS build #85782
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
b7a075e
to
b5e69a9
Compare
Would you be up for copying this config to a try builder -- likely adding onto here: rust/src/ci/github-actions/ci.yml Lines 643 to 652 in 9f75dbf
That way we can test this out without actually landing it and make sure it builds (and hopefully someone can verify the artifacts). |
@bors try |
⌛ Trying commit 82ec1fb10f172297a8859a2a91bf865a705fdb84 with merge ab06beff0b87a039398867d10c9e6570a1d5efc4... |
☀️ Try build successful - checks-actions |
At the very least it built something by the right name:
How would I get that artifact from S3? |
Ah, thanks to rustup-toolchain-installer I got it. Though as there is not |
Building that commit locally (and some hackery due to the explicit version check within I'll try using it tomorrow at work and see if I can get ahold a x86_64 Mac to test the full build from the try run. |
I threw the try build from that commit onto an x86_64 macOS machine using GitHub Actions here: https://github.com/badboy/gha-macos-rust-tests/runs/2710468159 It compiles a minimal Rust library to a static library.
I did not test that in the simulator itself, but I think this works exactly as planned. |
What are the next steps here, @Mark-Simulacrum? |
I think dropping the try part of this and updating the docs (platform support) to make this PR be the "make it tier 2" PR makes sense. I left a comment on the Zulip thread as well. |
Going to mark this as waiting-on-team; specifically a second on the MCP - rust-lang/compiler-team#428. |
@rustbot label +T-compiler (hope it's correct) |
@Mark-Simulacrum rust-lang/compiler-team#428 has been seconded, can |
I think we can now remove the "waiting on team" label @rustbot label -S-waiting-on-team |
82ec1fb
to
61640f2
Compare
rust-lang/compiler-team#428 has been accepted, I removed the test commit and force-pushed here. |
Once this is landed and we verified that the produced artifacts work I can change the documentation. |
Bump! @Mark-Simulacrum, as you gave feedback here earlier. Can we land this? |
Marked as waiting on review - I expect the answer is roughly "yes" but I'll need to take a look. Likely within the next week. |
Thanks! |
@bors r+ |
📌 Commit 61640f2 has been approved by |
☀️ Test successful - checks-actions |
…st, r=Mark-Simulacrum Add `aarch64-apple-ios-sim` as a possible target to the manifest This should allow rustup and similar to actually make use of this new target now. r? `@Mark-Simulacrum` Followup to rust-lang#85782
…st, r=Mark-Simulacrum Add `aarch64-apple-ios-sim` as a possible target to the manifest This should allow rustup and similar to actually make use of this new target now. r? ``@Mark-Simulacrum`` Followup to rust-lang#85782
…st, r=Mark-Simulacrum Add `aarch64-apple-ios-sim` as a possible target to the manifest This should allow rustup and similar to actually make use of this new target now. r? ```@Mark-Simulacrum``` Followup to rust-lang#85782
Part of the MCP 428 to promote this target to Tier 2.
This adds the aarch64-apple-ios-sim target as a tier 2 target, currently cross-compiled from our x86_64 apple builders. The compiler team has approved the addition per the MCP noted above, and the infrastructure team has not raised concerns with this addition at this time (as the CI time impact is expected to be minimal; this is only building std).