Disable macOS toolchain by default Copybara Import from https://github.com/bazelbuild/rules_cc/pull/755 BEGIN_PUBLIC Disable macOS toolchain by default (#755) You can get back the previous toolchain with `--repo_env=BAZEL_USE_LEGACY_MACOS_TOOLCHAIN=1` for now. Please report any issues you hit! Work towards https://github.com/bazelbuild/rules_cc/issues/754 Closes #755 END_PUBLIC COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/755 from keith:ks/disable-macos-toolchain-by-default 7dd05a4b5c4667e5ba7f59f9e0644a4c9289f448 PiperOrigin-RevId: 951038422 Change-Id: I1e6dfe54a372a9784d4b3d20d881dea8651990f7
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