bazel
/
rules_cc
mirror of https://github.com/bazelbuild/rules_cc
2
0
Fork 0
Code Issues Releases Activity
rules_cc/examples/my_c_compile
History
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
..
BUILD Add examples on how to integrate with rules_cc 2019-02-14 13:22:51 +01:00
foo.c Add examples on how to integrate with rules_cc 2019-02-14 13:22:51 +01:00
my_c_compile.bzl Add ctx argument to cc_common.configure_features 2019-05-08 01:46:21 -07:00