Google Git
Sign in
bazel / rules_cc / 5b73302b82d0d1da73ef6b2c26fae68d00c6a996
commit5b73302b82d0d1da73ef6b2c26fae68d00c6a996[log] [tgz]
authorKeith Smiley <keithbsmiley@gmail.com>Wed Nov 19 13:33:54 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Wed Nov 19 13:34:45 2025 -0800
tree736d1992e528b8e53bcf7da4a3be91b323a89f1a
parent933844609a1c1f0ea0ddb64c28d463e901f36f57 [diff]
Remove libopts toolchain variable

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

BEGIN_PUBLIC
Remove libopts toolchain variable (#495)

This appears to have been removed 9 years ago https://github.com/bazelbuild/bazel/commit/a8fc49b3ce772d98e6038a619cccdba81e76ac6d

Closes #495
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/495 from keith:ks/remove-libopts-toolchain-variable 6c4de8d9a81b57851396b9a8e9a4f5b493972c0e
PiperOrigin-RevId: 834423544
Change-Id: I315a178317af6c27c374b5013015c19d4ef92100
1 file changed
tree: 736d1992e528b8e53bcf7da4a3be91b323a89f1a
  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: