aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/docs/toolchains.md
diff options
context:
space:
mode:
authorGravatar Jacob Parker <jacob@solidangle.ca>2017-11-27 09:37:44 -0800
committerGravatar Copybara-Service <copybara-piper@google.com>2017-11-27 09:39:09 -0800
commit3e7ef36aa6f25200580fd235e71f9cb4cc8284aa (patch)
tree4a7b0cf6140f882915e8f9e2951c5a4b6116cb0c /site/docs/toolchains.md
parentbc4f97114dd6c82228c5b79868dcfdcd18818c24 (diff)
Fix link and usage of ToolchainInfo in docs
Closes #4158. PiperOrigin-RevId: 177028468
Diffstat (limited to 'site/docs/toolchains.md')
-rw-r--r--site/docs/toolchains.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/site/docs/toolchains.md b/site/docs/toolchains.md
index 57c69de329..8adca850a8 100644
--- a/site/docs/toolchains.md
+++ b/site/docs/toolchains.md
@@ -53,7 +53,7 @@ Defining a toolchain requires the following:
* **Toolchain rule** - a rule invoked in a custom build or test rule that
specifies the build tool configuration options particular to the toolchain
and supported [platforms](platforms.html) (for example, [`go_toolchain`](https://github.com/bazelbuild/rules_go/blob/master/go/private/go_toolchain.bzl)).
- This rule must return a [`ToolchainInfo` provider](skylark/lib/ToolchainInfo.html).
+ This rule must return a [`ToolchainInfo` provider](skylark/lib/platform_common.html#ToolchainInfo).
The toolchain rule is lazily instantiated by Bazel on an as-needed basis.
Because of this, a toolchain rule's dependencies can be as complex as needed,
including reliance on remote repositories, without affecting builds that do
@@ -78,7 +78,7 @@ that determines the CPU architecture for which Bazel builds the output.
```python
def _my_toolchain_impl(ctx):
- toolchain = platform.ToolchainInfo(
+ toolchain = platform_common.ToolchainInfo(
compiler = ctx.attr.compiler,
system_lib = ctx.attr.system_lib,
arch_flag = ctx.attr.arch_flag,