Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / e55d9c495f23149316f16263d5232047cfff95b8
commite55d9c495f23149316f16263d5232047cfff95b8[log] [tgz]
authorarmandomontanez <montanez.armando.l@gmail.com>Wed Feb 12 09:26:58 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Wed Feb 12 09:27:32 2025 -0800
tree1f67cb3dade7871dd7051fb3f3e10d2eeb4fb156
parent746a9e74ef8aff6461e57da32dd0f10762d23393 [diff]
Add assembly library to rule_based_toolchain example

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

BEGIN_PUBLIC
Add assembly library to rule_based_toolchain example (#361)

Adds a cc_library that compiles a tiny assembly file to provide some coverage for assembly actions in the rule_based_toolchain example.

Closes #361
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/361 from armandomontanez:add_asm_to_toolchain_example d8ff1b7fc7fe03fbc53fed9d13b79bb5e1ac2351
PiperOrigin-RevId: 726085163
Change-Id: I86b0e47f59328b73f09c05c3208713fc4f279c73
5 files changed
tree: 1f67cb3dade7871dd7051fb3f3e10d2eeb4fb156
  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: