Google Git
Sign in
bazel / rules_cc / 713572f05dc0c50bd7f368528d21c79e2b04793f
commit713572f05dc0c50bd7f368528d21c79e2b04793f[log] [tgz]
authorKeith Smiley <keithbsmiley@gmail.com>Tue Mar 04 01:35:46 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Tue Mar 04 01:36:18 2025 -0800
treec38647df4ed5d920c578b88c1ab960c1707403b9
parentdbc9cd5dd1085d621a6cc77669de436b2763a290 [diff]
Add objc_execution to all link actions

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

BEGIN_PUBLIC
Add objc_execution to all link actions (#359)

Without this it's not possible to create a rules based toolchain that
supports linking top level binaries which are linked through the Apple
specific bazel APIs.

Closes #359
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/359 from keith:ks/add-objc_execution-to-all-link-actions 1904f39e568e10e25b88bfac2688590aec44a0f5
PiperOrigin-RevId: 733231767
Change-Id: Ib8976fc00586a40f017cd86df276797a34996665
9 files changed
tree: c38647df4ed5d920c578b88c1ab960c1707403b9
  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: