Google Git
Sign in
bazel/rules_cc/refs/heads/main
commit
77eb752fc74b89e96e729ce9777854836fcbd9a2
[log]
author
David Zbarsky <dzbarsky@gmail.com>
Tue Jul 07 12:16:53 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Tue Jul 07 12:17:46 2026 -0700
tree
f1d91a07bf7d0512a29bcef8f098fdc4c3575f08
parent
21e14308c2afc7691f43295acc9852d9a6844f04 [diff]
Remove unused proto aspects semantics helper

Copybara Import from https://github.com/bazelbuild/rules_cc/pull/771

BEGIN_PUBLIC
Remove unused proto aspects semantics helper (#771)

## Summary

Remove `semantics.get_proto_aspects` and `_get_proto_aspects` from `cc/common/semantics.bzl`.

Both definitions were copied from Bazel builtins in July 2025 by 8e0a527eab2645a7ccd4d585b747779caacbc0b6 as part of the `cc_import` extraction. No rules_cc rule has referenced `semantics.get_proto_aspects`; `_get_proto_aspects` is referenced only by the unused struct field. Removing both definitions has no functional effect.

## Validation

- `buildifier -mode=check cc/common/semantics.bzl`
- `bazel build //tests/simple_import:foo_bin --jobs=4`

Closes #771
END_PUBLIC

Startblock:
  * // Put other blockers before this line to avoid churning.
  * has lgtm
  * is approved
  * and then
  * all comments are resolved
  * and then
  *[]
COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/771 from dzbarsky:codex/remove-proto-aspects-semantics 97f22502f0bf9a342be39076f0b79d55375efceb
PiperOrigin-RevId: 944028904
Change-Id: I20b91da1ecd5d0952d12bbabb3b7a15673705fb9
1 file changed
tree: f1d91a07bf7d0512a29bcef8f098fdc4c3575f08
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. cc/
  5. docs/
  6. examples/
  7. tests/
  8. .bazelignore
  9. .bazelrc
  10. .gitignore
  11. AUTHORS
  12. BUILD
  13. CODEOWNERS
  14. CONTRIBUTING.md
  15. googletest.patch
  16. ISSUE_TEMPLATE.md
  17. LICENSE
  18. local_bazel.bzl
  19. MODULE.bazel
  20. README.md
  21. WORKSPACE
  22. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status

This repository contains C, C++, and Objective-C language support for the Bazel build system.

For this module's main reference, see the Bazel documentation.

Get Started

Install Bazel

Follow the official instructions to Install Bazel.

Add rules_cc to your MODULE.bazel

Add the latest release to your MODULE.bazel project file.

Declare a build target

In a BUILD.bazel file, import and use the rules:

load("@rules_cc//cc:cc_binary.bzl", "cc_binary")

cc_binary(
    name = "hello_world",
    srcs = ["hello_world.cc"],
)

Build and run your project

Build and run your C/C++ binary with one command:

$ bazel run hello_world

To build the project without running the binary, use Bazel's build subcommand:

$ bazel build hello_world

Toolchains

Default autoconfigured toolchain

rules_cc includes an auto-configured toolchain that uses the local compiler installed on the host machine.

You can disable the autoconfigured C/C++ toolchain by adding the following Bazel flag to your project's .bazelrc file:

--repo_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1

Hermetic toolchains

Configuring a hermetic toolchain makes your build more deterministic. rules_cc itself does not yet offer a hermetic toolchain distribution. Other community owned and maintained projects offer hermetic C/C++ toolchains:

Contributing

Bazel and rules_cc are the work of many contributors. We appreciate your help!

To contribute, please read the contribution guidelines: CONTRIBUTING.md.

Note that the rules_cc use the GitHub issue tracker for bug reports and feature requests only. For asking questions see: