bazel
/
rules_cc
mirror of https://github.com/bazelbuild/rules_cc
2
0
Fork 0
Code Issues Releases Activity
248 Commits 15 Branches 20 Tags 1.9 MiB
Commit Graph

5 Commits

Author SHA1 Message Date
Googler 4de26b53a6 Remove need for exported_by or linked_statically_by 
For now we will restrict allowed exports to the same package. At the same time
static_deps should be used to take into account what should be linked into a
shared library.

RELNOTES:none
PiperOrigin-RevId: 294668451
Change-Id: Ia087519106983bfa9a980e471d3102ab391a53eb
 2020-02-12 08:01:50 -08:00
Googler 4a1c578fb0 C++: Move tools/cpp from bazel_tools to rules_cc 
Here we are duplicating bazel_tools/tools/cpp. The goal is for the BUILD files in bazel_tools/tools/cpp to have an alias that point to rules_cc. Then later on with the incompatible flag these aliases will no longer be valid.

Working towards #8743

RELNOTES:none
PiperOrigin-RevId: 264604076
Change-Id: I389702793a1a95b0990dce93577de2b7182e2e6b
 2019-08-21 07:30:04 -07:00
Googler eeec015f3e Update rules_cc for --incompatible_enable_cc_toolchain_resolution 
[Copybara import of https://github.com/bazelbuild/rules_cc/pull/14]

https://github.com/bazelbuild/bazel/issues/7260
Merge 3e6d3b9a4a into b308aae57f

PiperOrigin-RevId: 248296402
 2019-05-15 02:19:39 -07:00
hlopko 3d5980e5cb Add example writing custom rule that depends and is dependable from rules_cc 
RELNOTES: None.
PiperOrigin-RevId: 235869541
 2019-02-27 00:37:05 -08:00
hlopko 5743a325d1 Add examples on how to integrate with rules_cc 
RELNOTES: None.
PiperOrigin-RevId: 233926824
 2019-02-14 13:22:51 +01:00