Google Git
Sign in
bazel/rules_cc/refs/heads/main
commit
2c06f121b255ed6a7b3adf7a3d839e53a3085eac
[log]
author
Keith Smiley <keithbsmiley@gmail.com>
Mon Sep 07 09:31:29 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Mon Sep 07 09:33:40 2026 -0700
tree
29f5c271f93c0155f15504443416d33f5e7b63c5
parent
1d2e4cb24d720fb86c02f080c7a8d0c447ff948b [diff]
Add missing bsd link libraries (#859)

This mirrors this behavior from the clang driver:

https://github.com/llvm/llvm-project/blob/3e892fad65730692057da27bebb2e34d3ad7bde7/clang/lib/Driver/ToolChains/OpenBSD.cpp#L365-L366

The same does not apply for freebsd (I didn't check netbsd which isn't
supported here right now).

Alternatively we could use clang++ for linking directly instead of
clang, which would add these automatically, but that would make it
harder to disable these in the case you are linking pure C

Fixes https://github.com/bazelbuild/rules_cc/issues/857

Closes #859

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/859 from keith:ks/add-missing-openbsd-link-flags 70575fbff89f98fb4eb76db417e035133e8d767f
PiperOrigin-RevId: 977503273
Change-Id: Ifcb127ace43f5bad5f075de8dc7ae21d3182858d
1 file changed
tree: 29f5c271f93c0155f15504443416d33f5e7b63c5
  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: