Transitive Rules for Bazel Build Agent
eopeter opened this issue · comments
We are seeing an issue where Bazel's local_config_cc and local_config_cc_toolchains are UNKNOWN across a large swat of Xcode users that build with Bazel. What is needed to create transitive rules for Bazel and since you use Bazel at Google what is the best advice to allow xcode builds without Bazel components getting blocked.
We already have path scope for Xcode.
Having the users add rules for the binary in the _cc folder and muling creating pathscope but that is not ideal