Ivo List

> Ahh, I didn't see that rules_cc was being revived. Thanks! I've unclogged the pipelines! https://github.com/bazelbuild/rules_cc/blob/main/cc/defs.bzl#L178 > Does rules_cc have all of the changes to the crosstool/toolchain that have been...

> Will rules_cc become the canonical location? The issue we had before was it was hard to keep both up to date (going through review on both, dealing with versioning...

> I am relying on a potentially less problematic version of this over at [rules_meta](https://github.com/fmeum/rules_meta/blob/64ef1ae48adecb50d3101a7e7dff6c5c489cdc43/meta/internal/forwarding.bzl#L30) Why do you need to set the name? The rule is returned and eventually exported...

> I think it's going to break every single downstream project, including Bazel itself. It shouldn't break anything :)

The `rule.name` was never designed to support "anonymous rules" or to fix problems how rule classes are defined. I can see how it became useful, but I think those uses...

Downstream tests: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2641#01835443-ca23-4d89-b700-dd2ef89c8f7a Failures: - rules_android_ndk: doesn't have platform configuration, should disable cc_toolchain_resolution flag in bazelci, https://github.com/bazelbuild/rules_android_ndk/pull/20 - rules_foreign_cc: Mac + Android picks up local cc toolchain: https://github.com/bazelbuild/rules_foreign_cc/pull/967) - Google...

Failing test needs rules_cc 0.0.2 on bzlmod repository.

Hey, I think output paths are more concern of Configurability team? Or perhaps OSS? Please triage.

> I'm not familiar with the android toolchains at all so can you clarify to me here is there an issue with the build files in rules_foreign_cc examples that needs...

cc @rickeylev @haberman