Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/39e35dc103331d5bf369e0ea72daead2aeb52f66
commit
39e35dc103331d5bf369e0ea72daead2aeb52f66
[log] [tgz]
author
Corentin Kerisit <corentin.kerisit@gmail.com>
Tue Feb 24 19:05:33 2026 -0800
committer
Copybara-Service <copybara-worker@google.com>
Tue Feb 24 19:05:59 2026 -0800
tree
73a910ec613888ac818c3606c54c7309912f5338
parent
eec10ce53aac30239c714dec2076ddc46407ea8e [diff]
Add objc_compile to DEFAULT_SYSROOT_ACTIONS

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

BEGIN_PUBLIC
Add objc_compile to DEFAULT_SYSROOT_ACTIONS (#607)

When cross compiling objc, it is necessary to be able to pass `--sysroot` to `objc_compile` actions.

Closes #607
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/607 from cerisier:objc_sysroot 527806f3df7391e9a643f78258b34627c951babe
PiperOrigin-RevId: 874892922
Change-Id: I8e503e8d4842b041957f18d0a39d08ad95bc72b5
1 file changed
tree: 73a910ec613888ac818c3606c54c7309912f5338
  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: