-
Notifications
You must be signed in to change notification settings - Fork 116
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
Add Apple Silicon binary for CLI #779
Comments
I am not sure if it is worth the effort but how about modifying the github actions workflow here to include github hosted m1 runners and publish the binaries as a part of the release workflow 😅 |
It is a good idea. centraldogma-go isn't actively developed since the API of Central Dogma is stable. That said, it would be worth automatically releasing the binaries with GitHub Actions. |
If it is not actively developed, can I build it in my local and upload to at least provide a quick solution? Later a new issue can be opened regarding automated release pipeline? |
I added a script that generates binaries for well-known architectures and operating systems. |
Central Dogma CLI 0.1.0 has been released. https://github.com/line/centraldogma-go/releases/tag/0.1.0 Fixes: line#779
I did not know it was possible to compile for a specific architecture like that. I thought it was like iOS apps that need to be compiled on a Mac device 😆 Script looks good. |
Central Dogma CLI 0.1.0 has been released. https://github.com/line/centraldogma-go/releases/tag/0.1.0 Fixes: #779
… and operating systems (#60) We don't build and publish Central Dogma binaries on a regular basis yet. A build script and manual uploading would be sufficient at the moment. This will resolve the Apple silicon support in Central Dogma cli line/centraldogma#779
Currently, we only support amd64 for macOS CLI.
Go binaries are hosted in the release notes at https://github.com/line/centraldogma-go/releases/tag/0.0.1
We may build go CLI binaries for Apple Silicon and release it as 0.0.2
The text was updated successfully, but these errors were encountered: