Google Git
Sign in
bazel/rules_cc/170205b046318052d5009d595a337a65ff8fa425
commit
170205b046318052d5009d595a337a65ff8fa425
[log]
author
Keith Smiley <keithbsmiley@gmail.com>
Fri Apr 10 00:19:49 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Fri Apr 10 00:20:11 2026 -0700
tree
71a967f9885364d3e93b4e94e9c8889aeb1ee40b
parent
5bac5b40bfb25c77210925f506056bc2ea91b3ab [diff]
Make main_output public API

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

BEGIN_PUBLIC
Make main_output public API (#578)

This API allows creating shared libraries with custom filenames, not
just the default pattern. This is required to write a rule that produces
python native extensions which have entirely different output naming
formats than standard shared libraries.

This API has been around for years now so I assume it's well understood
enough and there isn't a clear alternative.

Closes #578
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/578 from keith:ks/make-main_output-public-api eff1404cf9b32ca2c2987db7e7021bf2780f89bc
PiperOrigin-RevId: 897523576
Change-Id: I591ef2117a8fe49afe1fab32eb57bc3437dada28
1 file changed
tree: 71a967f9885364d3e93b4e94e9c8889aeb1ee40b
  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: