github-actions[bot]
commented
1 year ago Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.
limdor
Description of the problem / feature request:
Bazel depends on rules_cc and it is exposed to end users, below I elaborate more why this is an issue:
Long time ago Bazel was saying that cc_binary, cc_library, cctest and the other cc* rules should be imported from rules_cc. However rules_cc was always saying that there is no need to use them yet. After several discussions it was clarified that migration to bazelbuild/rules_cc was put on hold and there is no need for the users to start using it.
The fact that bazel depends on rules_cc forces any user to use rules_cc.
More information about the discussions: bazelbuild/rules_cc#86 bazelbuild/rules_cc#92 bazelbuild/buildtools#923 bazelbuild/buildtools#952
Feature requests: what underlying problem are you trying to solve with this feature?
Do not make Bazel depend on rules_cc at least not exposing it to the user. It could be kept to build Bazel or for tests.
What's the output of
bazel info release?4.2.1
Any other information, logs, or outputs that you want to share?
This is similar to the issue https://github.com/bazelbuild/rules_go/issues/2949 In the moment that the issue for rules_go was created the situation was worst because there was no release for rules_cc