You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per title, this is more a question but I put it in issues as GH discussions are not open:
I tried to build for Mac M1 recently and I got the linker warning about the arm64e ABI and indeed the binary does not run on M1.
I decided to give my app a try an arm64 and I was surprised because it works.
I've read the posts about arm64e but I thought this was the only option for M1 and that things like signature are required (I'm using master osxcross which AFAII does not include the cctools PR to incorporate signature).
What is the recommendation here and what should work? Use arm64 till arm64e is stable? BTW, I also wanted to rebuild clang from the script and a few things fail, including the download even with the PR
The text was updated successfully, but these errors were encountered:
@philippe44 could not make the script to build clang either - I was aiming for llvm-15 (even after fixing the download issue). Ended-up just building LLVM out of band.
Per title, this is more a question but I put it in issues as GH discussions are not open:
I tried to build for Mac M1 recently and I got the linker warning about the arm64e ABI and indeed the binary does not run on M1.
I decided to give my app a try an arm64 and I was surprised because it works.
I've read the posts about arm64e but I thought this was the only option for M1 and that things like signature are required (I'm using master osxcross which AFAII does not include the cctools PR to incorporate signature).
What is the recommendation here and what should work? Use arm64 till arm64e is stable? BTW, I also wanted to rebuild clang from the script and a few things fail, including the download even with the PR
The text was updated successfully, but these errors were encountered: