Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/2310907573a3417594938f70b9c6b642b8eb3907
commit
2310907573a3417594938f70b9c6b642b8eb3907
[log]
author
Keith Smiley <keithbsmiley@gmail.com>
Tue Apr 28 08:26:46 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Tue Apr 28 08:27:25 2026 -0700
tree
2057c451bb7067d2c9ce78b21b66555965160c72
parent
804007dc387ccee143d37fa8c3506f980735f214 [diff]
Add local_defines to objc_library

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

BEGIN_PUBLIC
Add local_defines to objc_library (#629)

This mirrors cc_library

Fixes https://github.com/bazelbuild/bazel/issues/17482

Closes #629
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/629 from keith:ks/add-local_defines-to-objc_library 562f284c968c4ee7579cb13f85067680ce9017c9
PiperOrigin-RevId: 906992588
Change-Id: I7276f77b25cce1c2c4ee1168e2c63e4874d33de3
6 files changed
tree: 2057c451bb7067d2c9ce78b21b66555965160c72
  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. MODULE.bazel
  19. README.md
  20. renovate.json
  21. WORKSPACE
  22. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status

This repository contains a Starlark implementation of C++ rules in Bazel.

The rules are being incrementally converted from their native implementations in the Bazel source tree.

For the list of C++ rules, see the Bazel documentation.

Getting Started

Add the following to your WORKSPACE file:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "rules_cc",
    urls = ["https://github.com/bazelbuild/rules_cc/archive/refs/tags/<VERSION>.tar.gz"],
    sha256 = "...",
)

Then, in your BUILD files, import and use the rules:

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

cc_library(
    ...
)

Using the rules_cc toolchain

This repo contains an auto-detecting toolchain that expects to find tools installed on your host machine. This is non-hermetic, and may have varying behaviors depending on the versions of tools found.

There are third-party contributed hermetic toolchains you may want to investigate:

If you'd like to use the cc toolchain defined in this repo, add this to your WORKSPACE after you include rules_cc:

load("@rules_cc//cc:repositories.bzl", "rules_cc_dependencies", "rules_cc_toolchains")

rules_cc_dependencies()

rules_cc_toolchains()

Migration Tools

This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.

Legacy fields migrator

Script that migrates legacy crosstool fields into features (incompatible flag, tracking issue).

TLDR:

bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \
  --input=my_toolchain/CROSSTOOL \
  --inline

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: