Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/refs/heads/upstream/main
commit
8d64d255b75e625c2f904c2c88c6e4581ecab55c
[log]
author
Googler <bgorshenev@google.com>
Fri Jun 19 08:29:37 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Fri Jun 19 08:30:00 2026 -0700
tree
57e353d4847313cc7874a657d8befd9ed0b9ae0d
parent
8169167529a5c39dd194cb30f933da025c6bdef6 [diff]
Reorganize rules_cc buildkite config.

Use yaml merging for target lists and flags; we've had issues with those not being consistently set between e.g. test and coverage

Replace mentions of bazel 6 with bazel_less_than_9

Add coverage to ubuntu2004_rolling for consistency (can consider not running coverage on as many things as we currently do).

Use Bazel 7/8/9.x in rules_based toolchains for consistency instead of specific  versions.

Tests migrated from builtins_bzl seem to work fine with legacy bazels, eliminating the head/rolling/9 target selection distinction I introduced in that change.

Leaving the no_windows and no_macos tags in for now but we'll probably want to delete them in the future.

PiperOrigin-RevId: 934941969
Change-Id: I6eea589460fbcfcab698afb0804c4a04a98bd5a0
1 file changed
tree: 57e353d4847313cc7874a657d8befd9ed0b9ae0d
  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: