Google Git
Sign in
bazel/rules_cc/d0fa9b7ad62718bc1cb8ebb2f546d6651cf88ab7
commit
d0fa9b7ad62718bc1cb8ebb2f546d6651cf88ab7
[log]
author
Fabian Meumertzheim <fabian@meumertzhe.im>
Mon Nov 17 10:26:22 2025 -0800
committer
Copybara-Service <copybara-worker@google.com>
Mon Nov 17 10:26:54 2025 -0800
tree
7afe155d7e329e12a84fd82931a2f9d429c2d0f1
parent
109e43da9b210aa1806ac27bb640d2233c9703ce [diff]
Fix `invalid linker name in argument '-fuse-ld=ld64.lld'` on macOS

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

BEGIN_PUBLIC
Fix `invalid linker name in argument '-fuse-ld=ld64.lld'` on macOS (#516)

This is caused by this extra warning being printed by the clang invocation used to detect the linker path:

```
ld64.lld: warning: directory not found for option -L/usr/local/lib
```

Fix this by making the match for the path more specific.

Closes #516
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/516 from fmeum:patch-2 8e75534c8fb13fa979bacd421ad131c2b00623d7
PiperOrigin-RevId: 833396773
Change-Id: I5bf17c5f27337984533e1f9e49d214ff74c7435b
1 file changed
tree: 7afe155d7e329e12a84fd82931a2f9d429c2d0f1
  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. googletest.patch
  16. ISSUE_TEMPLATE.md
  17. LICENSE
  18. MODULE.bazel
  19. README.md
  20. renovate.json
  21. WORKSPACE
  22. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit 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: