Google Git
Sign in
bazel / rules_cc / 1582328dbf1c9f39a6dc373f42319fbe0f2dfebc
commit1582328dbf1c9f39a6dc373f42319fbe0f2dfebc[log] [tgz]
authorCorentin Kerisit <corentin.kerisit@gmail.com>Mon May 05 16:13:36 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Mon May 05 16:14:14 2025 -0700
tree71bd0211d519d3eb2968beb19764c8af1ef6dc1f
parent7aa70df89558af435685ece35a3cb37c6ceb226b [diff]
Add support for stripopts for strip_flags:feature

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

BEGIN_PUBLIC
Add support for stripopts for strip_flags:feature (#407)

#324 introduced strip_flags as per https://github.com/bazelbuild/bazel/blob/0a9ebcf4ed0c8b59628f660f8002e6da0b325c2e/src/main/java/com/google/devtools/build/lib/rules/cpp/CppActionConfigs.java#L1358-L1371 but striopts were not implemented.

Closes #407
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/407 from cerisier:stripopts 3990c4788f6b0a222e237229c2a087e5ac90456b
PiperOrigin-RevId: 755110078
Change-Id: I509bc0ab07ee8741beb436280575f3772a8c5e84
1 file changed
tree: 71bd0211d519d3eb2968beb19764c8af1ef6dc1f
  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. ISSUE_TEMPLATE.md
  16. LICENSE
  17. MODULE.bazel
  18. README.md
  19. renovate.json
  20. WORKSPACE
  21. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status
  • Postsubmit + Current Bazel Incompatible flags 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: