Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
runtime: tracking bug for ARM-based macOS and GOOS/GOARCH values #38485
The ARM-based Mac rumors of the past couple years continue to heat up (e.g. https://www.theverge.com/2020/3/27/21196611/arm-macbook-desktop-apple-2021-release-date)
Has anybody given any thought to what we're going to do with runtime.GOOS and runtime.GOARCH if/when that happens, so we don't add ambiguity between
Changing GOARCH seems out.
Perhaps some magic behavior like we did for
If there's new API, might be nice to get that in earlier. But OTOH, don't want to jump the gun if rumors don't pan out.
If darwin/arm64 doesn't work for macos,
I've thought about whether we should have GOOS=macos
Interesting to note that way back when, we could have done
I think the suggestion here is:
This will potentially break any existing mobile programs that test
This suggests that for 1.15 we should
gomobile uses ios tag and also we use the ios tag in crypto/x509 package. gomobile sets GOOS/GOARCH for crosscompile so it needs to use the right value depending on the go version. I don't think that's too difficult. In addition to gomobile, cc/ @eliasnaur <email@example.com> for gio, @hajimehoshi for ebiten users…
On Fri, May 1, 2020 at 2:38 PM cherrymui ***@***.***> wrote: I think (but not sure) gomobile sets ios tag, to distinguish iOS emulator on x86 vs. macOS. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#38485 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGESL63JC4FILQFUNGUQH3RPMJJPANCNFSM4MJZNOPQ> .
Also interesting is that Apple currently has macOS, iOS, iPadOS, tvOS, and watchOS.