Skip to content

Conversation

d0ugal
Copy link
Contributor

@d0ugal d0ugal commented Sep 18, 2025

  • Add darwin/arm64 to PLATFORMS in config.mk to ensure it's built and published
  • This enables ARM64 macOS builds in GitHub Actions workflows
  • Cross-compilation from Linux runners will produce darwin-arm64 binaries

- Add darwin/arm64 to PLATFORMS in config.mk to ensure it's built and published
- This enables ARM64 macOS builds in GitHub Actions workflows
- Cross-compilation from Linux runners will produce darwin-arm64 binaries
@d0ugal d0ugal requested a review from a team as a code owner September 18, 2025 11:35
@d0ugal d0ugal requested review from ka3de and mem September 18, 2025 11:35
@mem
Copy link
Contributor

mem commented Sep 18, 2025

  • Add darwin/arm64 to PLATFORMS in config.mk to ensure it's built and published

It's going to be built, but it's not going to be published.

  • This enables ARM64 macOS builds in GitHub Actions workflows
  • Cross-compilation from Linux runners will produce darwin-arm64 binaries

Note that this will only build the native binaries, and that's running in linux-amd64 and linux-arm64.

From there, the other job uses that output to push files to the release, but since the darwin binary is not there, it doesn't get pushed.

I'm guessing the build (as in "make build") doesn't work in Darwin, does it? I would be surprised if that workflow worked without changes in that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants