Add best effort toolchain feature docs Copybara Import from https://github.com/bazelbuild/rules_cc/pull/701 BEGIN_PUBLIC Add best effort toolchain feature docs (#701) I took a pass at doing some base level documentation for all the magic features that apply to cc toolchains. This doesn't exhaustively list their behavior, but it gives a useful bit of context for folks. This is useful for folks who are trying to enable specific things and who are writing their own toolchains. I tried to put enough comments in here about how this doesn't mean it's treated as public API. Closes #701 END_PUBLIC Tested: TAP --sample ran all affected tests and none failed [] COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/701 from keith:ks/add-best-effort-toolchain-feature-docs a3d5890bb21f486f7efc3119d617fa75219a4fd0 PiperOrigin-RevId: 947387247 Change-Id: Ia10796f8289aa973bda5fc5226acf7d4a0558921
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