Google Git
Sign in
bazel / rules_cc / 2a5a16f0f813e5b8a9c379887ab9e0ba2cbfd66e
commit2a5a16f0f813e5b8a9c379887ab9e0ba2cbfd66e[log] [tgz]
authorarmandomontanez <montanez.armando.l@gmail.com>Thu Feb 06 13:34:38 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Thu Feb 06 13:35:09 2025 -0800
treeba571adfe9cb4f069c266b29d797c81da1c2c225
parentc9b3ccb0bb42c71a9a4a603b2472ae5a130a6363 [diff]
Override legacy features with cc_feature_set

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

BEGIN_PUBLIC
Override legacy features with cc_feature_set (#338)

Modifies experimental_replace_legacy_action_config_features slightly to make it override legacy features rather than just reimplement them as args. This should prevent duplicate arguments for the features that are re-implemented.

Closes #338
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/338 from armandomontanez:origin/experimental_override_legacy_features 42b5f5d4807f4444a8630e1c8678aabcd061a368
PiperOrigin-RevId: 724056412
Change-Id: I220b195b359afdea37afd50d655f871eea127e20
7 files changed
tree: ba571adfe9cb4f069c266b29d797c81da1c2c225
  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

There is no need to use rules from this repository just yet. If you want to use rules_cc anyway, 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: