mirror of https://github.com/bazelbuild/rules_cc
f97190f039
BEGIN_PUBLIC Remove feature requirements from tools. It's such a niche use case, adds a fair amount of complexity, and there are multiple alternatives available: * Now that we're using rule based things, you should just be able to add a bazel flag and select on it in your tool definition. * If you really want precisely that behaviour, you can make your feature add "--use-foo-tool" to the args, and make your tool a wrapper tool that reads the command-line argument, and if provided, invokes a different tool. END_PUBLIC PiperOrigin-RevId: 657383729 Change-Id: Idb4f3ad66dc92d48ef81a1e8875bf6d3ba215aa4 |
||
|---|---|---|
| .. | ||
| common | ||
| compiler | ||
| private | ||
| proto | ||
| runfiles | ||
| toolchains | ||
| BUILD | ||
| action_names.bzl | ||
| cc_binary.bzl | ||
| cc_import.bzl | ||
| cc_library.bzl | ||
| cc_shared_library.bzl | ||
| cc_test.bzl | ||
| cc_toolchain_config_lib.bzl | ||
| defs.bzl | ||
| extensions.bzl | ||
| find_cc_toolchain.bzl | ||
| objc_import.bzl | ||
| objc_library.bzl | ||
| repositories.bzl | ||
| system_library.bzl | ||
| toolchain_utils.bzl | ||