Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / 5be90a4e04e64df0e9d26382e1006d3df21aaa91
commit5be90a4e04e64df0e9d26382e1006d3df21aaa91[log] [tgz]
authorYun Peng <pcloudy@google.com>Thu Nov 28 03:58:39 2024 -0800
committerCopybara-Service <copybara-worker@google.com>Thu Nov 28 03:59:31 2024 -0800
tree901271528b24b5ff5e7c1da298372e0b8a5ebf20
parent8395ec0172270f3bf92cd7b06c9b5b3f1f679e88 [diff]
Expose get_cpu_value in toolchain_config_utils.bzl

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

BEGIN_PUBLIC
Expose get_cpu_value in toolchain_config_utils.bzl (#283)

Addressing https://github.com/bazelbuild/bazel-central-registry/issues/3260#issuecomment-2505731130

Closes #283
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/283 from bazelbuild:meteorcloudy-patch-5 8d7f986ebc60c2c22f15adef1e663c474e78299a
PiperOrigin-RevId: 700977422
Change-Id: I979446d5d79d8da465ec538632326d6d2c6932f7
1 file changed
tree: 901271528b24b5ff5e7c1da298372e0b8a5ebf20
  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: