Google Git
Sign in
bazel / rules_cc / 4ac36f7cd4f74ece2bafcdbb79574151dbc91e02
commit4ac36f7cd4f74ece2bafcdbb79574151dbc91e02[log] [tgz]
authorKeith Smiley <keithbsmiley@gmail.com>Wed Feb 12 10:04:56 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Wed Feb 12 10:05:35 2025 -0800
tree90182ea4b5dfcb8113fd240f673092b6f027e24b
parente55d9c495f23149316f16263d5232047cfff95b8 [diff]
Add random_seed feature args and feature

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

BEGIN_PUBLIC
Add random_seed feature args and feature (#340)

Closes #340
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/340 from keith:ks/add-random_seed-feature-args-and-feature 3374cb498e983ae36ce64b50dc43acf986814bc0
PiperOrigin-RevId: 726098531
Change-Id: I5851bd89b7ce8df1d3a21f64f0e6960320145b02
3 files changed
tree: 90182ea4b5dfcb8113fd240f673092b6f027e24b
  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
  • Postsubmit + Current Bazel Incompatible flags 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: