Keith Smiley
Keith Smiley
what target are you trying to build in the case that you see this? it sounds like you might not have a valid CC target or something
if you put it in the deps of a macos_command_line_application or something similar does it fail the same way? Building the target directly doesn't really make sense because it doesn't...
Do you have a custom C++ toolchain? If so that could also be the original issue
Ok can you upload a sample project so I can debug?
What bazel version are you using? using 5.3.1 seems to work: ``` % bz version Bazelisk version: development Build label: 5.3.1 Build target: bazel-out/darwin_arm64-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar Build time: Mon Sep 19 17:37:11...
Ah do you have a full Xcode install? Or just the command line tools? You might need a full install if you only have the command line tools. And I...
Um, potentially. We don't test / claim to support command line tools only for the Apple rules. You can test rules_apple @ HEAD (which requires bazel 6.x rolling releases) and...
I think technically we could fix this specific case, the issue is in the C++ toolchain setup in bazel itself for the non-Xcode toolchain, but likely you would hit more...
You can actually work around this by setting `BAZEL_TARGET_SYSTEM=arm64-apple-macosx12.3` (or some similarly formatted triple) in the environment to correctly set the toolchain's triple. Without that bazel sets it to `local`...
I only added this to iOS right now, figured we could add as needed to other rules ¯\_(ツ)_/¯