Add M1 Mac Support on Testing and Doc #65
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spuder
force-pushed
the
patch-1
branch
3 times, most recently
from
e015837
to
89dfb65
Compare
update readme fix readme
|
Example of this working: https://github.com/spuder/yeet |
|
This PR is mostly on automated testing and examples since the M1 support has been supported already without any change required. Anyway, thanks very much for the contribution! |
wangyoucao577
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apple hardware on M1 macs require
arm64builds.This makes M1 cpus a first class citizen
Note: While it is desirable to compile applications for arm64, its not currently possible to run these builds until microsoft/github creates arm64 runners in github actions