Add -mmacosx-version-min back to default toolchain Copybara Import from https://github.com/bazelbuild/rules_cc/pull/780 BEGIN_PUBLIC Add -mmacosx-version-min back to default toolchain (#780) Without this compiler behavior is non-heremetic based on the host OS version This reverts commit 2d10ebab2b9d40ecdff973921709d5986c33f728. Closes #780 END_PUBLIC COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/780 from keith:ks/add-mmacosx-version-min-back-to-default-toolchain 13492bd4fa2d363ab9833be73913ab2a0bad043e PiperOrigin-RevId: 943641157 Change-Id: Ia5b1c6766b62cc3fc6b3188369e9e9ee89ec2609
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