Google Git
Sign in
bazel/rules_cc/6dd21bed4595d7afbe0e390ec84bdd2d3953a0a7
commit
6dd21bed4595d7afbe0e390ec84bdd2d3953a0a7
[log]
author
Jeremy Nimmer <jeremy.nimmer@tri.global>
Wed Oct 29 12:06:12 2025 -0700
committer
Copybara-Service <copybara-worker@google.com>
Wed Oct 29 12:06:48 2025 -0700
tree
aca028710a209f446e59719a44104c98b5bcd573
parent
01c27aa8f0a2b75fc5de58aa98015d5ce389e68e [diff]
Support prefer_pic_for_opt_binaries in linux auto-detecting toolchain

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

BEGIN_PUBLIC
Support prefer_pic_for_opt_binaries in linux auto-detecting toolchain (#456)

See the demo project [example.zip](https://github.com/user-attachments/files/21706101/example.zip) for reproduction.

Without this fix, `foo.cc` is compiled twice (once PIC, once non-PIC).  With this fix, it is correctly only compiled once because the `.bazelrc` requests `build --features=prefer_pic_for_opt_binaries`.

Closes #456
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/456 from jwnimmer-tri:prefer_pic_for_opt_binaries ac8ec34b3e6aaa025da1758729cd6a90af5d3e5f
PiperOrigin-RevId: 825651000
Change-Id: I972d2bc2600268f32296c84412162f2874cc0eaa
1 file changed
tree: aca028710a209f446e59719a44104c98b5bcd573
  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: