Google Git
Sign in
bazel/rules_cc/ef3c571d8d8c7038bc28fcddced8749bb6c5d6e7
commit
ef3c571d8d8c7038bc28fcddced8749bb6c5d6e7
[log]
author
armandomontanez <montanez.armando.l@gmail.com>
Wed Mar 05 05:36:59 2025 -0800
committer
Copybara-Service <copybara-worker@google.com>
Wed Mar 05 05:37:39 2025 -0800
tree
e4f74c72144a2fc37f11a76088009ae01e100502
parent
713572f05dc0c50bd7f368528d21c79e2b04793f [diff]
Add missing requires_not_none expansion in strip_flags

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

BEGIN_PUBLIC
Add missing requires_not_none expansion in strip_flags (#369)

Fixes the strip_flags expansion that broke when the input_file variable was changed to be optional.

Closes #369
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/369 from armandomontanez:fix_input_file_expansion 67462c76a4c81a607f53d38e0ed4c6d3547bb53d
PiperOrigin-RevId: 733694885
Change-Id: I3bcc39292736cc3e60bb5aece1cda5d09e92328b
1 file changed
tree: e4f74c72144a2fc37f11a76088009ae01e100502
  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: