Update win_cross.md docs.
mini_installer now works, so mention that.
Apparently the cross-built chrome has crashing renderers which seems
somewhat important, so mention that too.
TBR=hans
Bug: 495204
Change-Id: I773544f73b24a58c5738fb9545a9b6f56f83c486
Reviewed-on: https://chromium-review.googlesource.com/879302
Reviewed-by: Nico Weber <[email protected]>
Commit-Queue: Nico Weber <[email protected]>
Cr-Commit-Position: refs/heads/master@{#530933}diff --git a/docs/win_cross.md b/docs/win_cross.md
index 926a552..f1cfcd8 100644
--- a/docs/win_cross.md
+++ b/docs/win_cross.md
@@ -8,7 +8,7 @@
* goma. Sorry. ([internal bug](http://b/64390790)) You can use the
[jumbo build](jumbo.md) for faster build times.
-* mini_installer ([bug](https://crbug.com/762073))
+* renderer processes crash at startup ([bug](https://crbug.com/803591))
* on Mac hosts, building a 32-bit chrome ([bug](https://crbug.com/794838))
All other targets build fine (including `chrome`, `browser_tests`, ...).
@@ -51,6 +51,12 @@
ninja -C out/gnwin base_unittests.exe
+## Copying and running chrome
+
+A convenient way to copy chrome over to a Windows box is to build the
+`mini_installer` target. Then, copy just `mini_installer.exe` over
+to the Windows box and run it to install the chrome you just built.
+
## Running tests on swarming
You can run the Windows binaries you built on swarming, like so:
