-
Notifications
You must be signed in to change notification settings - Fork 282
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
Arm64 for Apple silicon #2360
Comments
When investigating support for Apple M chips, we found that there was no GitHub CI support. It is possible to cross build for Apple chips but we would not be able to run any tests to check that everything was working correctly. When GitHub adds support then someone can make the changes in Exiv2. In #2173, another user requested adding support for Apple M chips. In there, there is a discussion on building Exiv2 from source that you may find helpful. I am closing this issue as it is a duplicate of #2173. |
AFAIK, exiv2 0.27.5 is available from MacPorts for arm64, don't know about Homebrew... Edit: On Homebrew as well. |
There is now a runner for M1 actions:
(but it is not free for now) |
You can use the FlyCI's M1 and M2 runners. Our runners are on average 2x faster and 2x cheaper than GitHub's AND we have a free tier for OSS projects (see below). Install InstructrionsEasily replace your M1 runners: jobs:
ci:
- runs-on: macos-latest
+ runs-on: flyci-macos-large-latest-m1
steps:
- name: 👀 Checkout repo
uses: actions/checkout@v4 Or try the M2 runners: jobs:
ci:
- runs-on: macos-latest
+ runs-on: flyci-macos-large-latest-m2
steps:
- name: 👀 Checkout repo
uses: actions/checkout@v4 Pricing
500 mins/month Free for Public ReposIf your repo is public, then FlyCI offers 500 mins/month of free M1 runner usage with the Best Regards, |
Is your feature request related to a problem?
There are more and more mac computer will use M chip, but the nightly build still only has x86_64 arch, could you please add universal binary which includes both x86_64 and arm64?
Thanks
The text was updated successfully, but these errors were encountered: