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

5 Commits

Author SHA1 Message Date
Marcel Hlopko 6cd7e75fc4 Update examples for platforms 2019-05-24 14:52:19 +02: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 b308aae57f Add ctx argument to cc_common.configure_features 
In order to migrate C++ rules to platforms, we need the access to the C++
configuration fragment in Starlark APIs. All existing APIs have already access
to it, but cc_common.configure_features doesn't. This change adds a
ctx argument to configure_features.

This is the migration needed for
https://github.com/bazelbuild/bazel/issues/7793, and is part of the effort for
https://github.com/bazelbuild/bazel/issues/6516.

If the rule doesn't depend on cpp fragment yet, you will have to add `fragments
=['cpp']` argument to the rule() call.

Note that this behavior is only available in Bazel 0.25 (to be released this month).

RELNOTES: None.
PiperOrigin-RevId: 247171967
 2019-05-08 01:46:21 -07:00
Googler 2d3bc12294 Remove duplication of feature_configuration 
RELNOTES: None.
PiperOrigin-RevId: 236652129
 2019-03-04 07:53:44 -08: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