Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / cc91caec0a86ef2619b7879e15a6bb23f4a90f96
commitcc91caec0a86ef2619b7879e15a6bb23f4a90f96[log] [tgz]
authorMarkus Hofbauer <markus.hofbauer@tum.de>Fri Dec 13 23:42:24 2024 -0800
committerCopybara-Service <copybara-worker@google.com>Fri Dec 13 23:42:59 2024 -0800
tree9fe96ec7c8b05fd992662226d1ab9ff17a8e20d5
parent34f0e1f038cff9bf28d65d101c806b48f35bf92e [diff]
Fix attribute name in cc_tool docs

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

BEGIN_PUBLIC
Fix attribute name in cc_tool docs (#290)

The attribute [here](https://github.com/bazelbuild/rules_cc/blob/34f0e1f038cff9bf28d65d101c806b48f35bf92e/cc/toolchains/tool.bzl#L66) is named `src` while the example calls is `executable`. This PR renames the example to `src`.

Closes #290
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/290 from hofbi:fix-cc-tool-example 0cd1fc44bf98b67f5bffe1991eeecdb6c874c6c9
PiperOrigin-RevId: 706134958
Change-Id: I68d6fde87caa8d6670196e081d54c8ec9548861e
2 files changed
tree: 9fe96ec7c8b05fd992662226d1ab9ff17a8e20d5
  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: