Google Git
Sign in
bazel / rules_cc / d48233ae8d396fe66ee36bb58707b7114ed102bc
commitd48233ae8d396fe66ee36bb58707b7114ed102bc[log] [tgz]
authorGoogler <noreply@google.com>Wed May 28 22:08:39 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Mon Jun 02 11:10:13 2025 -0700
tree06399397fd912967a065497e6374e3850310a490
parent5202ddc05a30742fb0f3c09e354c3e840b636cc1 [diff]
rules_cc: FreeBSD 10.x and later use `libc++`, not `libstdc++`.

<https://wiki.freebsd.org/NewC++Stack> notes that FreeBSD 10.x (Jan 2014) and
onwards switched from the old GNU `libstdc++` to LLVM `libc++`, in line with the
rest of the base system switching toolchains from GNU to LLVM.

In fact, this was previously fixed by bazelbuild/bazel#14860, but apparently
that was after the great partitioning of `rules_cc`, and _this_ half of the
change got lost when we started using those build files instead.  The result is
that the `cc_binary` link step of a C++ binary will fail for the lack of a C++
standard library implementation.

This might fix the observable effects of bazelbuild/rules_cc#161 --- though that
issue correctly notes that a C compiler should not be a C++ linker, which is how
we have ended up even dealing with this problem.

PiperOrigin-RevId: 764561487
Change-Id: I535b432c90d93339fd7a8b6b70cf2a1a0d854bc8
1 file changed
tree: 06399397fd912967a065497e6374e3850310a490
  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: