Google Git
Sign in
bazel / rules_cc / 56897752c092569bba02da18b945033bcb42f2ad
commit56897752c092569bba02da18b945033bcb42f2ad[log] [tgz]
authorGoogler <pcloudy@google.com>Thu May 06 08:44:28 2021 -0700
committerCopybara-Service <copybara-worker@google.com>Thu May 06 08:44:55 2021 -0700
tree55468a55c7ec069333bba0c31d56fb233b37dc7a
parentc612c9581b9e740a49ed4c006edb93912c8ab205 [diff]
Remove restriction on generate_pdb_file to be only used in dbg and fastbuild mode

Users may want to build in opt mode and still want the pdb file to be a linking action output.
See https://github.com/bazelbuild/rules_cc/issues/94#issuecomment-828254895

RELNOTES: None
PiperOrigin-RevId: 372351216
Change-Id: I1b8a8709014deb4abdb13db387e185cd08f408d7
1 file changed
tree: 55468a55c7ec069333bba0c31d56fb233b37dc7a
  1. .bazelci/
  2. cc/
  3. distro/
  4. examples/
  5. tests/
  6. third_party/
  7. tools/
  8. .gitignore
  9. AUTHORS
  10. BUILD
  11. CODEOWNERS
  12. CONTRIBUTING.md
  13. internal_deps.bzl
  14. internal_setup.bzl
  15. ISSUE_TEMPLATE.md
  16. LICENSE
  17. README.md
  18. renovate.json
  19. WORKSPACE
README.md

C++ rules for Bazel

  • Postsubmit Build status
  • Postsubmit + Current Bazel Incompatible flags Build status

This repository contains 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

There is no need to use rules from this repository just yet. If you want to use rules_cc anyway, 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/TODO"],
    sha256 = "TODO",
)

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

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

cc_library(
    ...
)

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: