Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/22c49c3f2a169a859228801dc91b3ae2ad4c3d46
commit
22c49c3f2a169a859228801dc91b3ae2ad4c3d46
[log]
author
Corentin Kerisit <corentin.kerisit@gmail.com>
Tue Oct 28 02:01:46 2025 -0700
committer
Copybara-Service <copybara-worker@google.com>
Tue Oct 28 02:02:35 2025 -0700
tree
660a1c93d3001a97641fe2682bd17edb7ffe6b48
parent
34d652e37c9dcff9bcc7e44eaaaf513e972bdb10 [diff]
Pass -no_warning_for_no_symbols flag to libtool on macos

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

BEGIN_PUBLIC
Pass -no_warning_for_no_symbols flag to libtool on macos (#503)

This was the default in Bazel before Starlarkification.

Closes #503
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/503 from cerisier:no_warning_for_no_symbols cd9d7ebe9a0d09cdbadf9ba00cc8b3d15986e17c
PiperOrigin-RevId: 824916957
Change-Id: I5e43216e89bfd5daae1b70336440dd678f549df7
3 files changed
tree: 660a1c93d3001a97641fe2682bd17edb7ffe6b48
  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: