Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / 187afc0f8932f751bfa508c747b1b4150b110844
commit187afc0f8932f751bfa508c747b1b4150b110844[log] [tgz]
authorKeith Smiley <keithbsmiley@gmail.com>Mon Feb 03 15:05:56 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Mon Feb 03 15:06:22 2025 -0800
tree9bf01879551348a47be060b26a7e49bf2b03694f
parent1ad8898fd629d9d13d3aa24d4ac043df30ff0e99 [diff]
Add missing objc arc variable extensions

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

BEGIN_PUBLIC
Add missing objc arc variable extensions (#343)

ObjC compilation in bazel has a separate set of variables that can be
used by the crosstool

https://github.com/bazelbuild/bazel/blob/4d295906bd144f4bcbf89342d3d3cd7cc5de15ca/src/main/starlark/builtins_bzl/common/objc/compilation_support.bzl#L37-L40

Closes #343
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/343 from keith:ks/add-missing-objc-arc-variable-extensions b173c2dc8e11b4f0a58dde20584edf29ff44b439
PiperOrigin-RevId: 722813606
Change-Id: I7a0e6ee68facb58d6f30368df799f78dbb02bd70
1 file changed
tree: 9bf01879551348a47be060b26a7e49bf2b03694f
  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: