|author||Googler <email@example.com>||Fri Mar 06 05:44:46 2020 -0800|
|committer||Copybara-Service <firstname.lastname@example.org>||Fri Mar 06 05:45:05 2020 -0800|
C++: Move default linker flags with libs after libraries Default linker flags contains flags like -lstdc++ which should come after the user libraries. The library flags are removed from default linker flags and added to link_libs instead which comes after user libraries. See #9254 Incompatible flag bug: https://github.com/bazelbuild/bazel/issues/10905 I introduce a new method to repositories ctx that allows checking the value of a Starlark semantic option from a repository rule. RELNOTES:none PiperOrigin-RevId: 299336105 Change-Id: I81b9ee0c72e2a2252b406f1c584997389a530e40
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
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.
bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \ --input=my_toolchain/CROSSTOOL \ --inline
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: