Google Git Google Git
Sign in
bazel/rules_cc/b4e0b771512463ad22d3e453dce33300694bf54c
commit
b4e0b771512463ad22d3e453dce33300694bf54c
[log]
author
Googler <bgorshenev@google.com>
Mon Sep 14 19:00:28 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Mon Sep 14 19:01:07 2026 -0700
tree
ab2752ee72a25b1837e3db0f89846f26064bd42e
parent
77064f0caa37d0fb2232f54feb5fba275aeebbd3 [diff] 
Make feature names constants.

Armando mentioned something that made me think of this again; I'm still not sure if this is worth implementing (every new feature will require editing a widely-loaded constants file). We might as well discuss this to see if it's worth it.

b/339328480 suggests implementing something to ensure that a string constant can't be passed directly. I'm unsure if that's a good idea (we could add a wrapper around is_enabled that checks this)

TODO: feature names in errors, feature names looked up in other data structures, cc_helper_internal (pending a refactor of that file to deal with loading issues).

Startblock:
  * // Put other blockers before this line to avoid churning.
  * has lgtm
  * is approved
  * and then
  * all comments are resolved
  * and then
  *[] allows unknown commit
PiperOrigin-RevId: 981490892
Change-Id: Ic97c46d4ef6f1d2c68168bbeb270484c2be686a9
29 files changed
tree: ab2752ee72a25b1837e3db0f89846f26064bd42e
  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. CONTRIBUTING.md
  14. googletest.patch
  15. ISSUE_TEMPLATE.md
  16. LICENSE
  17. local_bazel.bzl
  18. MODULE.bazel
  19. README.md
  20. WORKSPACE
  21. 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: