diff options
author | John Cater <jcater@google.com> | 2018-01-03 09:19:35 -0800 |
---|---|---|
committer | Copybara-Service <copybara-piper@google.com> | 2018-01-03 09:21:47 -0800 |
commit | 283666d7547da8e76c8a929decb14eac9c200941 (patch) | |
tree | 59c1eb1b7d0961c93d31a4c29833a7ce4486408a /site/docs/toolchains.md | |
parent | 693abdcf0947bcc9f8010ea139b5b7b37eaa0a0e (diff) |
Expose platform flags for documentation purposes.
Also remove experimental tag from platform and toolchain flags in docs.
Fixes #4372.
Change-Id: I4e8f29273b52fbaabf9c97d1a7563f817601653f
PiperOrigin-RevId: 180678722
Diffstat (limited to 'site/docs/toolchains.md')
-rw-r--r-- | site/docs/toolchains.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/site/docs/toolchains.md b/site/docs/toolchains.md index f5c910eea2..96f012becf 100644 --- a/site/docs/toolchains.md +++ b/site/docs/toolchains.md @@ -31,7 +31,7 @@ When a target requests a toolchain, Bazel checks the list of registered toolchains and creates a dependency from the target to the first matching toolchain it finds. To find a matching toolchain, Bazel does the following: -1. Looks through the registered toolchains, first from the `--experimental_extra_toolchains` +1. Looks through the registered toolchains, first from the `--extra_toolchains` flag, then from the `registered_toolchains` calls in the project's `WORKSPACE` file. @@ -147,7 +147,7 @@ toolchain( Once the toolchain rule and definition exist, register the toolchain to make Bazel aware of it. You can register a toolchain either via the project's -`WORKSPACE` file or specify it in the `--experimental_extra_toolchains` flag. +`WORKSPACE` file or specify it in the `--extra_toolchains` flag. Below is an example toolchain registration in a `WORKSPACE` file: |