Google Git Google Git
Sign in
bazel/rules_cc/3086932435b3cb5ba3966f6953d3344839d6df14
commit
3086932435b3cb5ba3966f6953d3344839d6df14
[log]
author
Googler <bgorshenev@google.com>
Mon Sep 21 17:59:15 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Mon Sep 21 17:59:53 2026 -0700
tree
4c886ef7c57ace1006d134dc210beb67ed00191e
parent
cd02576bfad2a205d6adbe8b9faa91871354e603 [diff] 
Use feature_names constants, following up on previous change.

This covers cc_helper_internal, the new coverage_enabled/coverage_instrumented features, and usages of is_requested.

Toolchain configs still use strings probably want to change those but then we'd want to change all the toolchain definitions for consistency, need to think about those a bit more.
Tests still use strings, not sure how I feel about that.

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: 985624401
Change-Id: I3dda2b6b950cfd29e9fc0e11c473a82309c3bb57
6 files changed
tree: 4c886ef7c57ace1006d134dc210beb67ed00191e
  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: