commit | a74452e9109e28e70c9c6632799c8c37905776fa | [log] [tgz] |
---|---|---|
author | Googler <plf@google.com> | Tue Apr 21 08:37:54 2020 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 21 08:38:17 2020 -0700 |
tree | 8a37c7ff52bb385cb01f5e3898fdcbec592ecf50 | |
parent | 77099ee80d15004ddbac96234761c0a564479131 [diff] |
C++: Optimize cc_shared_library 1. Don't pop from the front of the list being iterated on 2. Don't visit the same node_label more than once RELNOTES:none PiperOrigin-RevId: 307610981 Change-Id: I9b35a27a1bdabafbe290d1ff23eeb4659b07d554
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.
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( ... )
This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.
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
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