Check private cc_common.link arguments once Copybara Import from https://github.com/bazelbuild/rules_cc/pull/822 BEGIN_PUBLIC Check private cc_common.link arguments once (#822) Combine the archive-output predicate with the existing cc_common.link private-argument predicates so callers receive one check_private_api invocation. Preserve existing allowlist behavior, argument normalization, and caller-stack depth. Validation: 51 remote C++ common and link-build-variable tests passed. Closes #822 END_PUBLIC Tested: TAP train for global presubmit queue [] COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/822 from dzbarsky:codex/starlarkify-link-private-api-checks 87ec078b62b14ac1a26564625898221479035080 PiperOrigin-RevId: 958324374 Change-Id: I00eff33a6c72c382cf8d149bc7337ce72bf5823e
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.
Follow the official instructions to Install Bazel.
Add the latest release to your MODULE.bazel project file.
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 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
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
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:
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:
rules_cc mailing list#cc on slack.bazel.build