Google Git
Sign in
bazel/rules_cc/12566743936ef587f59f357fd3a3597a980c90f2
commit
12566743936ef587f59f357fd3a3597a980c90f2
[log]
author
David Zbarsky <dzbarsky@gmail.com>
Wed Aug 05 07:47:27 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Wed Aug 05 07:47:59 2026 -0700
tree
6f3f7849f4867d8759d010609d05a33fb24c39b6
parent
eb9a5988f833b65c903fb71908dbc6b1c6529029 [diff]
Use Starlark dynamic-library symlinks in C++ linking

Copybara Import from https://github.com/bazelbuild/rules_cc/pull/810
+ Two javatest fixes.

BEGIN_PUBLIC
Use Starlark dynamic-library symlinks in C++ linking (#810)

Route both remaining direct `_cc_internal.dynamic_library_symlink` calls in `cc_linking_helper.bzl` through the existing Starlark `dynamic_library_symlink` implementation. The existing implementation preserves artifact naming, symlink registration, and its compatibility fallback for older Bazel versions.

Update the ThinLTO symlink regression to accept the Starlark `Symlink` action mnemonic and the native `SolibSymlink` compatibility fallback.

Validation: `buildifier -mode=check` and 89 passing ThinLTO, C++ binary, and import analysis tests.

Closes #810
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/810 from dzbarsky:codex/starlarkify-linker-dynamic-symlinks eb6c27e2b9523a51851b50de77e34eb9a282395e
PiperOrigin-RevId: 959656478
Change-Id: Ie5dbb3c109511a62f2bb74fed747eab4b2984814
2 files changed
tree: 6f3f7849f4867d8759d010609d05a33fb24c39b6
  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. local_bazel.bzl
  19. MODULE.bazel
  20. README.md
  21. WORKSPACE
  22. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status

This repository contains C, C++, and Objective-C language support for the Bazel build system.

For this module's main reference, see the Bazel documentation.

Get Started

Install Bazel

Follow the official instructions to Install Bazel.

Add rules_cc to your MODULE.bazel

Add the latest release to your MODULE.bazel project file.

Declare a build target

In a BUILD.bazel file, import and use the rules:

load("@rules_cc//cc:cc_binary.bzl", "cc_binary")

cc_binary(
    name = "hello_world",
    srcs = ["hello_world.cc"],
)

Build and run your project

Build and run your C/C++ binary with one command:

$ bazel run hello_world

To build the project without running the binary, use Bazel's build subcommand:

$ bazel build hello_world

Toolchains

Default autoconfigured toolchain

rules_cc includes an auto-configured toolchain that uses the local compiler installed on the host machine.

You can disable the autoconfigured C/C++ toolchain by adding the following Bazel flag to your project's .bazelrc file:

--repo_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1

Hermetic toolchains

Configuring a hermetic toolchain makes your build more deterministic. rules_cc itself does not yet offer a hermetic toolchain distribution. Other community owned and maintained projects offer hermetic C/C++ toolchains:

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: