Add/Update external Reclient build instructions
Bug: b/291868532
Change-Id: I54e6225ab01e12141957949d5c8c35b32e5062d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5159847
Reviewed-by: Takuto Ikuta <[email protected]>
Commit-Queue: Andrew Williams <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1244750}
diff --git a/docs/windows_build_instructions.md b/docs/windows_build_instructions.md
index 773241e..3d06652c 100644
--- a/docs/windows_build_instructions.md
+++ b/docs/windows_build_instructions.md
@@ -242,20 +242,19 @@
source-level debugging but call stacks still have function names. Changing
`symbol_level` requires recompiling everything.
+When invoking ninja, specify 'chrome' as the target to avoid building all test
+binaries as well.
+
#### Use Reclient
-In addition, Google employees should use reclient, a distributed compilation system.
+In addition, Google employees should use Reclient, a distributed compilation system.
Detailed information is available internally but the relevant gn arg is:
* `use_remoteexec = true`
Google employees can visit
-[go/building-chrome-win#setup-remote-execution](http://go/building-chrome-win#setup-remote-execution)
-for more information.
-
-When invoking ninja, specify 'chrome' as the target to avoid building all test
-binaries as well.
-
-Still, builds will take many hours on many machines.
+[go/building-chrome-win#setup-remote-execution](https://goto.google.com/building-chrome-win#setup-remote-execution)
+for more information. For external contributors, Reclient does not support
+Windows builds.
#### Use Goma (deprecated)
