Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/0d150d5268c362c0da2cbb497d9c03d1466c2bee
commit
0d150d5268c362c0da2cbb497d9c03d1466c2bee
[log]
author
Keith Smiley <keithbsmiley@gmail.com>
Wed Aug 05 06:56:04 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Wed Aug 05 06:56:38 2026 -0700
tree
4510ffc9534f513e881ce285dcd44f8bd8ed66a4
parent
df61b8c4f5d2760f9a01bd3d9473167373b42e39 [diff]
Allow 'includes = ["."]' in the root of the repo

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

BEGIN_PUBLIC
Allow 'includes = ["."]' in the root of the repo (#625)

This isn't really something you want to do in a large project, but this
is a very common requirement of open source libraries that are part of
the BCR. Today they are buildable when pulled in through bzlmod, but not
when you're testing changes to them directly.

Bazel already adds an `-iquote .` to the root of the repo for all
builds, so if something is in your dependency tree, you can include it
relatively with the path from the root. If you want to guard against
that you can use layering_check to make sure deps are explicitly
defined.

Fixes https://github.com/bazelbuild/rules_cc/issues/453

Closes #625
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/625 from keith:ks/allow-includes-.-in-the-root-of-the-repo b8d3bf3bcfb725068efb51a4841f355e83347f8e
PiperOrigin-RevId: 959633803
Change-Id: Iedd96ea9a3d484ba712db03edb7a9cd3228706b2
1 file changed
tree: 4510ffc9534f513e881ce285dcd44f8bd8ed66a4
  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: