Open yyuting opened 8 months ago
In your example your first command works because of your platform_mappings
file. If you want the second command to work you'd have to add that entry to the platform_mappings
file as well
Thanks! According to the discussion in #1658 , I thought we no longer need platform_mappings
on bazel 7.x+. Or am I missing something?
hrm yea interesting. so the problem is that currently --ios_multi_cpus
takes precedence over the --platforms
setting. This happens with the default value even though you're not passing it explicitly. It's because of our current transition for this. We are following in google's footsteps here and it looks like they're still using the same behavior there too. I'm not sure what implications of changing that would be.
this is actually the same as https://github.com/bazelbuild/rules_apple/issues/1650
thanks for the explanation!
on Bazel 7.0.2 and rule_apple 3.3.0, I'm unable to use
ios_build_test
andios_application
with the default platform from apple_support.Here's a minimum example with a hello world
ios_build_test
target. https://github.com/yyuting/bazel_apple_platform/tree/mainThe target is set to only be compatible with ios arm64 device (not simulator).
Build succeeds with a custom platform and explicit platform mapping:
bazel test //:ios_build_tests --platforms=//:platform_ios
But building with the default
ios_arm64
platform from apple_support would fail, it seems apple rules is picking up ios_sim_arm64 for the cc_library that the ios_build_test target depends on.bazel test //:ios_build_tests --platforms=@build_bazel_apple_support//platforms:ios_arm64
Here's the error message: