bazel
/
rules_cc
mirror of https://github.com/bazelbuild/rules_cc
2
0
Fork 0
Code Issues Releases Activity

Fix rules_cc copybara 

PiperOrigin-RevId: 682280542
Change-Id: Ie5f9dbc05f4d87dbe14b2392a21a23ef0c3ea9a4
This commit is contained in:
Googler 2024-10-04 05:22:54 -07:00 committed by Copybara-Service
parent b1bea517b7
commit fd72f9e62a
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
cc/toolchains/actions.bzl
View File

@ -40,7 +40,7 @@ cc_action_type = rule(
`cc_action_type` rules are used to associate arguments and tools together to `cc_action_type` rules are used to associate arguments and tools together to
perform a specific action. Bazel prescribes a set of known action types that are used to drive perform a specific action. Bazel prescribes a set of known action types that are used to drive
typical C/C++/ObjC actions like compiling, linking, and archiving. The set of well-known action typical C/C++/ObjC actions like compiling, linking, and archiving. The set of well-known action
types can be found in [//cc/toolchains/actions:BUILD](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/actions/BUILD). types can be found in [//third_party/bazel_rules/rules_cc/cc/toolchains/actions:BUILD](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/actions/BUILD).
It's possible to create project-specific action types for use in toolchains. Be careful when It's possible to create project-specific action types for use in toolchains. Be careful when
doing this, because every toolchain that encounters the action will need to be configured to doing this, because every toolchain that encounters the action will need to be configured to

4
cc/toolchains/impl/variables.bzl
View File

@ -75,7 +75,7 @@ def cc_variable(name, type, **kwargs):
it's not possible to declare custom variables. it's not possible to declare custom variables.
For a full list of available variables, see For a full list of available variables, see
[//cc/toolchains/varaibles:BUILD](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/variables/BUILD). [//third_party/bazel_rules/rules_cc/cc/toolchains/varaibles:BUILD](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/variables/BUILD).
Example: Example:
``` ```
@ -91,7 +91,7 @@ def cc_variable(name, type, **kwargs):
Args: Args:
name: (str) The name of the outer variable, and the rule. name: (str) The name of the outer variable, and the rule.
type: The type of the variable, constructed using `types` factory in type: The type of the variable, constructed using `types` factory in
[//cc/toolchains/impl:variables.bzl](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/impl/variables.bzl). [//third_party/bazel_rules/rules_cc/cc/toolchains/impl:variables.bzl](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/impl/variables.bzl).
**kwargs: [common attributes](https://bazel.build/reference/be/common-definitions#common-attributes) that should be applied to this rule. **kwargs: [common attributes](https://bazel.build/reference/be/common-definitions#common-attributes) that should be applied to this rule.
""" """
_cc_variable(name = name, type = json.encode(type), **kwargs) _cc_variable(name = name, type = json.encode(type), **kwargs)

2
cc/toolchains/tool.bzl
View File

@ -102,7 +102,7 @@ This can help work around errors like:
providers = [ToolCapabilityInfo], providers = [ToolCapabilityInfo],
doc = """Declares that a tool is capable of doing something. doc = """Declares that a tool is capable of doing something.
For example, `//cc/toolchains/capabilities:supports_pic`. For example, `//third_party/bazel_rules/rules_cc/cc/toolchains/capabilities:supports_pic`.
""", """,
), ),
}, },

2
cc/toolchains/tool_map.bzl
View File

@ -75,7 +75,7 @@ def cc_tool_map(name, tools, **kwargs):
`CXX=/path/to/clang++` environment variables that most build systems use to determine which `CXX=/path/to/clang++` environment variables that most build systems use to determine which
tools to use for a given action. To simplify usage, some actions have been grouped together (for tools to use for a given action. To simplify usage, some actions have been grouped together (for
example, example,
[//cc/toolchains/actions:cpp_compile_actions](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/actions/BUILD)) to [//third_party/bazel_rules/rules_cc/cc/toolchains/actions:cpp_compile_actions](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/actions/BUILD)) to
logically express "all the C++ compile actions". logically express "all the C++ compile actions".
In Bazel, there is a little more granularity to the mapping, so the mapping doesn't follow the In Bazel, there is a little more granularity to the mapping, so the mapping doesn't follow the