Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / 0f1635c334108b91d5df2fb93cc33251cdd36c09
commit0f1635c334108b91d5df2fb93cc33251cdd36c09[log] [tgz]
authorCorentin Kerisit <corentin.kerisit@gmail.com>Mon Nov 24 09:47:46 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Mon Nov 24 09:48:25 2025 -0800
tree82098a8a43068f8eff4c93f576e58c9c20dcd545
parent2a18367fa71b9c0fe0325d65171e9d9e70d59990 [diff]
Pass -D to libtool on macos

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

BEGIN_PUBLIC
Pass -D to libtool on macos (#504)

This was the default in Bazel before Starlarkification.

```
-D     When building a static library, set archive contents' user ids, group ids, dates, and file modes to reasonable defaults. This allows libraries created with identical input to be identical to
       each other, regardless of time of day, user, group, umask, and other aspects of the environment.
```

Closes #504
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/504 from cerisier:pass_d_to_libtool 1a72fd88524a3e133cad8ee8d083002991e29454
PiperOrigin-RevId: 836261812
Change-Id: I9e307bf771e9d07986cdf68715dafb595676359d
3 files changed
tree: 82098a8a43068f8eff4c93f576e58c9c20dcd545
  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: