Add Windows ThinLTO arguments Copybara Import from https://github.com/bazelbuild/rules_cc/pull/747 BEGIN_PUBLIC Add Windows ThinLTO arguments (#747) Windows rule-based toolchains currently reuse ELF LLD ThinLTO plugin options and `/dev/null`, which are not valid for LLD's COFF driver or Windows backend actions. This change selects the LLD COFF ThinLTO options, uses `/start-lib` and `/end-lib` for object-file groups, and uses `NUL` for indexless Windows backend actions. This allows Windows toolchains that use LLD and provide `supports_start_end_lib` to enable rules_cc distributed ThinLTO. Closes #747 END_PUBLIC COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/747 from dzbarsky:zbarsky/win-lto fad3b18c5d6d3d69a8825d3888470ee8c4df91d3 PiperOrigin-RevId: 940818026 Change-Id: I11c6542a1020983b20e3490af2b2e49b388105ac
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