-
Notifications
You must be signed in to change notification settings - Fork 260
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
How to build for multiple architectures #2419
Comments
I see the same with |
Hrm did this ever work? Might be worth bisecting (or just testing the first sha that had this rule) A potential fix is to fetch deps from |
This doesn't seem to have worked as far back as 1.0.0 using Bazel 5 |
macos_*
rules fail to build for multiple architectures
My use case right now is we want to release a macOS application and just noticed it was running under Rosetta because it was building using x86_64 github runners. |
Maybe this generally never worked and then it became virtually obsolete because xcframeworks solve multi-archs (even for macOS although it feels unnecessary since there aren't platform arch conflicts) |
What rule is the application target? With a macOS application rule it should work. And if it fails because a macos_dynamic_framework is in the dependency tree you should replace that with a macos_framework. Theoretically the former should only be used for distribution |
Ah that was it, makes sense. Thanks! So in summary for folks:
|
I guess we cant use |
yea, I guess that was less of a priority since you can still use a fat framework there, but then i guess you hit this even on macOS? |
probably worth a split_deps fix |
When trying to build a FAT binary for a
macos_dynamic_framework
using--macos_cpus=x86_64,arm64
I hit the following error:This build works as-is when building for a single architecture. This is with Bazel
6.4.0
and rules_apple3.2.1
The text was updated successfully, but these errors were encountered: