-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Source code project support Apple Silicon natively #2872
Comments
me too |
@blackberrier we are internally using Gradle 5 and have no immediate requirement to move to Gradle 7+. However, if you are willing to upgrade to gradle 7 and contribute, I will help review the code and merge in the open source repo. |
This is legit the only place in the entire Github — as of today1 — where "osx_arm-v8" is mentioned. I think it's a Gradle problem. But I am too new to Gradle to know where the issue is; let alone propose a fix Footnotes
|
I am so confused. Why is this the only result? That search was how I found this link, and I'm not even using this project, just a barebones JNI project. Edit: |
I have a working branch for Apple Silicon / ARM and relevant instructions that I just pushed to this branch and opened a PR (Note: it wasn't clear what value the "build scan" Gradle plugin was providing - and it was the only thing I couldn't get working on ARM). The builds, distribution and tests all work. https://github.com/jeffsteinmetz/azkaban/tree/jeffs/apple-silicon-arm |
See PR ^^ |
Issue Description
I am reading source code on Apple M1 device, but I get some faults. The error message indicates that Gradle is not support for M1 chips.
Gradle has support for Apple Silicon since version 7.0. Now we are using Gradle version 4.6 in the project, so I got the previous faults.
Expected Behavior
Open azkaban gradle project without error
Things todo
compile
toimplementation
az-exec-util
Current progress
I have done step 1 and 2, and get stuck in step 3, with error message
Invalid NativePlatform: osx_arm-v8
The text was updated successfully, but these errors were encountered: