commit | 03ae87bea3528232327ba4f4d4b544d14b518875 | [log] [tgz] |
---|---|---|
author | Googler <plf@google.com> | Thu Nov 28 07:52:56 2019 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Nov 28 07:53:21 2019 -0800 |
tree | b9ebf784082a85423e9bfa0e3f2d2e40c811fee3 | |
parent | 1f87a00b388c29337553581ec94a17985f121031 [diff] |
C++: Updates linking for cc_shared_library Order of libraries should be topological sort when constructing depset for LinkingContext. Also remove condition that failed when it shouldn't with a valid combination of libraries. RELNOTES:none PiperOrigin-RevId: 282943411 Change-Id: I0b727c4cdeaf484e1c4177a714542eae7f167613
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:
#cc
on slack.bazel.build