-
Notifications
You must be signed in to change notification settings - Fork 654
[Feature] Gitversion support for apple silicon #2668
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
Comments
Unfortunately we currently do not support the new silicon. Even though there is some level of support for ARM provided by Libgit2sharp, but we do not support it official |
Any plans on supporting it in the future? |
I think we should support it in long term, the issue is we are not able to build it in GitHubAction or AzurePipelines at the moment. When that is available we could add support for the M1 |
I have not tried this yet, but here is the full error I see from homebrew:
Has anyone tried using the --build-from-source? Were you successful? |
Support for M1 in .NET 6 is underway, but still far from complete. Until both .NET and LibGit2Sharp have full support for M1, GitVersion won't be able to provide full support for M1. |
For me I need to run the arm64 version with docker which is supported in dotnet as far as I am aware. It would be great if there could be a arm64 docker image. https://docs.docker.com/desktop/multi-arch/ |
any updates on this one? |
@MuhKuh7 actually it should already support osx-arm64 starting with 5.8.1 https://github.com/GitTools/GitVersion/releases/tag/5.8.1 |
@arturcic thx, will 5.8.1 be available on homebrew (https://formulae.brew.sh/formula/gitversion) soon? |
unfortunately for the homebrew we ned to have the dotnet formula for version 6.0, that's something @asbjornu was working on. So for now no, you can only use the tar.gz version for now |
I would like to use gitversion on my apple silicon.
Installing using brew gives me:
Error: dotnet: no bottle available!
Try to use the docker image gives me:
The text was updated successfully, but these errors were encountered: