Google Git
Sign in
bazel / rules_cc / ff06b70246c165fd0ca011e1b6b5a195762c949b
commitff06b70246c165fd0ca011e1b6b5a195762c949b[log] [tgz]
authorAustin Schuh <austin.linux@gmail.com>Sun Jul 13 17:17:54 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Sun Jul 13 17:19:24 2025 -0700
treec19af46319b1393bc9b10560c0e460a9d02cdce8
parent4d4fc0725aa48ea2332da1ba0b6ba1aca61e8093 [diff]
Add fastbuild_compile_flags to unix_cc_toolchain_config

Copybara Import from https://github.com/bazelbuild/rules_cc/pull/301

BEGIN_PUBLIC
Add fastbuild_compile_flags to unix_cc_toolchain_config (#301)

We already have dbg_compile_flags and opt_compile_flags.  This add symetry to enable pulling fastbuild flags out of .bazelrc files and into the toolchain.

Closes #301
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/301 from AustinSchuh:fastbuild_flags 4e06396851b1ca4edaad891266c88eb1ab1ec85d
PiperOrigin-RevId: 782686208
Change-Id: I02c8f569903ca938926485cd19bab75cc9414467
1 file changed
tree: c19af46319b1393bc9b10560c0e460a9d02cdce8
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. cc/
  5. docs/
  6. examples/
  7. tests/
  8. .bazelignore
  9. .bazelrc
  10. .gitignore
  11. AUTHORS
  12. BUILD
  13. CODEOWNERS
  14. CONTRIBUTING.md
  15. ISSUE_TEMPLATE.md
  16. LICENSE
  17. MODULE.bazel
  18. README.md
  19. renovate.json
  20. WORKSPACE
  21. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status

This repository contains a Starlark implementation of C++ rules in Bazel.

The rules are being incrementally converted from their native implementations in the Bazel source tree.

For the list of C++ rules, see the Bazel documentation.

Getting Started

Add the following to your WORKSPACE file:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "rules_cc",
    urls = ["https://github.com/bazelbuild/rules_cc/archive/refs/tags/<VERSION>.tar.gz"],
    sha256 = "...",
)

Then, in your BUILD files, import and use the rules:

load("@rules_cc//cc:defs.bzl", "cc_library")

cc_library(
    ...
)

Using the rules_cc toolchain

This repo contains an auto-detecting toolchain that expects to find tools installed on your host machine. This is non-hermetic, and may have varying behaviors depending on the versions of tools found.

There are third-party contributed hermetic toolchains you may want to investigate:

If you'd like to use the cc toolchain defined in this repo, add this to your WORKSPACE after you include rules_cc:

load("@rules_cc//cc:repositories.bzl", "rules_cc_dependencies", "rules_cc_toolchains")

rules_cc_dependencies()

rules_cc_toolchains()

Migration Tools

This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.

Legacy fields migrator

Script that migrates legacy crosstool fields into features (incompatible flag, tracking issue).

TLDR:

bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \
  --input=my_toolchain/CROSSTOOL \
  --inline

Contributing

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: