mirror of https://github.com/bazelbuild/rules_cc
5e848c1434
BEGIN_PUBLIC Remove the "data" attribute from cc_action_type_config. Technically speaking, data shouldn't be associated with action types. Instead, data should be associated with either a tool or a set of flags. For example, instead of the cc_compile action having the header files as a data dependency, the "include_paths" cc_arg should instead declare `data = <header files>`. This will allow us to, once we have a fully starlark-ified c++ toolchain, do much finer-grained dependencies. This will allow us to, for example, not provide header files to the action when the user enables the feature "nostdlib". END_PUBLIC PiperOrigin-RevId: 642434412 Change-Id: Id16fe05a1c86bbaf4718cd36a15f8a9d6afb0163 |
||
|---|---|---|
| .. | ||
| compiler | ||
| private | ||
| proto | ||
| runfiles | ||
| toolchains | ||
| BUILD | ||
| action_names.bzl | ||
| cc_toolchain_config_lib.bzl | ||
| defs.bzl | ||
| extensions.bzl | ||
| find_cc_toolchain.bzl | ||
| repositories.bzl | ||
| system_library.bzl | ||
| toolchain_utils.bzl | ||