Google Git
Sign in
bazel / rules_cc / 9c91c036a100abfc0c1aa54ae30a7214d28686fa
commit9c91c036a100abfc0c1aa54ae30a7214d28686fa[log] [tgz]
authorKeith Smiley <keithbsmiley@gmail.com>Wed Feb 12 15:23:39 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Wed Feb 12 15:24:11 2025 -0800
tree552b677177aacdab607532f74fb22ad693336b12
parent4ac36f7cd4f74ece2bafcdbb79574151dbc91e02 [diff]
Add strip_flags

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

BEGIN_PUBLIC
Add strip_flags (#324)

Previously the strip action appeared to be entirely invalid since no
flags were passed to strip. I believe this is because the strip action
was configured in the legacy feature code without any extra features,
just directly on the action.

Closes #324
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/324 from keith:ks/add-strip_flags 79f114357b020bae2c5faab29f15df44365d420e
PiperOrigin-RevId: 726219472
Change-Id: Icb7685353896d0d4b392432637fa8cf64dc61c0d
2 files changed
tree: 552b677177aacdab607532f74fb22ad693336b12
  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: