bazel/rules_cc
2
0
Fork 0
mirror of https://github.com/bazelbuild/rules_cc synced 2024-11-30 22:41:22 +00:00
Code Issues Releases Activity
331 commits 16 branches 20 tags 1.9 MiB
Commit graph

12 commits

Author SHA1 Message Date
Christopher Peterson Sauer ab8b67a0ab Move examples from deprecated find_cpp_toolchain -> find_cc_toolchain 2022-04-05 23:58:12 -07:00
Googler 426f721323 Automatic code cleanup. 
PiperOrigin-RevId: 407085810
Change-Id: I6cac435d8e0e89f97405c7b3923d1891da78740b
 2021-11-02 08:13:14 -07:00
Googler 88ef31b429 Update rules_cc to use the correct toolchain type (@bazel_tools//tools/cpp:toolchain_type). 
PiperOrigin-RevId: 361158816
Change-Id: Ief011b23ddb9bdf3b49237f90fa631b6f916e8de
 2021-03-05 09:10:23 -08:00
Googler 991eb349bf Internal change 
PiperOrigin-RevId: 340301767
Change-Id: Iccab5010d3fd6e77c08fcdc140cdc1e461185b0d
 2020-11-02 13:19:59 -08:00
Googler 699ec52985 Internal change 
PiperOrigin-RevId: 339925655
Change-Id: Icde35bf6acb72a382e0253fcf9fb5a10d80a5feb
 2020-10-30 13:05:57 -07:00
Googler 16ad606329 Internal change 
PiperOrigin-RevId: 339887089
Change-Id: Ic511ced72381f847f5d1b9159f299b6e474a47de
 2020-10-30 09:41:38 -07:00
Googler f95239adde Update rules_cc to use the toolchain transition. 
This is phase 2 of of the switch to toolchain transitions. See https://github.com/bazelbuild/bazel/issues/11584 for details.

PiperOrigin-RevId: 334808134
Change-Id: Ie198b07359d4fd45368755c4cc223e397f0e8fb0
 2020-10-01 07:19:37 -07:00
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