-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Create a aarch64-apple-ios-sim
target for rustc
#81632
Comments
Is #77484 relevant at all? Can the same path be followed? |
Awesome find @shepmaster I'll try doing this! If successful I'll open a similar PR :) |
Ran into this now too. Happy to help here as well. |
@badboy I did but having trouble I've pushed my changes here: https://github.com/deg4uss3r/rust/tree/degausser/aarch64_apple_ios_sim More than happy to work with you on this Jan! |
I'll try to get a dev environment set up and then I'll take a look. |
I built the toolchain successfully, but when I try to compile my project (with either
I think I've missed a setting in the build config I'm using, because the normal nightly compiles fine :(
Edit looks like I will try off |
Yeah, that looks like upstream breakage in |
Yeah I added the patch mentioned in that issue and am getting further but:
which Xcode still seems to be getting x86_64 somewhere:
I tried replacing all the
but got:
|
I believe my current version is working but there's something off in my Xcode project that I need to figure out:
|
Ah, you're building a binary? Yeah, that seems to sort-of work now? |
It was just a test to see if the simulator is working at all XD. Yeah my
|
Currently in our application we cannot run the iOS simulator on M1 machines because it is expecting
x86_64
architecture. Forcingarm64
using therustc
targetaarch64-apple-ios
can build the project and ship the application but this targets the iOS Device SDK, and will not build in the simulator for testing with this error:rustc
should provide anaarch-apple-ios-sim
target that uses the iOS Simulator SDK.The text was updated successfully, but these errors were encountered: