bazel/rules_cc
2
0
Fork 0
mirror of https://github.com/bazelbuild/rules_cc synced 2024-11-27 20:43:26 +00:00
Code Issues Releases Activity
324 commits 15 branches 20 tags 1.9 MiB
Commit graph

9 commits

Author SHA1 Message Date
Marcel Hlopko 0e4443f2ca Instead disable the buildifier warning 2020-05-04 11:59:13 +02:00
Marcel Hlopko 65436199d8 Duh 2020-05-04 11:59:13 +02:00
Marcel Hlopko e8781b53aa Fix repositories.bzl 2020-05-04 11:59:10 +02:00
Copybara-Service e7c97c3af7 Merge pull request #45 from hlopko:fix_cc_configure 
PiperOrigin-RevId: 278612577
Change-Id: I70ed5cfba7bc5c5ee5cb0db45e0f072a36a49cff
 2019-11-05 06:40:31 -08:00
Marcel Hlopko 4f8676f6ca Add rules_cc_toolchains to repositories.bzl 
This is the new entry point for registering C++ toolchains (replacing
implicit cc_configure()).

While at it, fix one misnamed function.
 2019-11-01 16:36:34 +01:00
Florian Weikert 6cc7e712fb Fetch dependencies through the Bazel federation. 
As a result of this commit, rules_cc now contains the required bzl files to be tested as part of the Bazel federation.
 2019-08-09 15:41:00 +02:00
Marcel Hlopko ec70973809 Fix sha hash of the skylib release, and put mirror first 
I have no clue what happened, but it seems skylib release on github was
changed after rules_cc started to depend on it.
 2019-06-28 18:46:43 +02:00
Vladimir Chebotarev 4afc266bf0
Placed GitHub release first for @skylib. 
See bazelbuild/bazel-skylib#164.
 2019-06-27 13:51:21 +03:00
Googler d36c8d400c Refactor rules_cc to follow https://docs.bazel.build/versions/master/skylark/deploying.html 
RELNOTES: None.
PiperOrigin-RevId: 253736769
Change-Id: Ib13ecb077559f890aa3cc207b7ec1a53ac18d553
 2019-06-18 00:21:44 -07:00
Renamed from cc/deps.bzl (Browse further)