[Fuchsia] Add install-build-deps.sh and KVM to build notes.
Change-Id: I18b6fb62596e00cb8315c5eabd0360cdbe48f59a
Reviewed-on: https://chromium-review.googlesource.com/c/1318803
Commit-Queue: Wez <[email protected]>
Reviewed-by: Sergey Ulanov <[email protected]>
Cr-Commit-Position: refs/heads/master@{#605615}diff --git a/docs/fuchsia_build_instructions.md b/docs/fuchsia_build_instructions.md
index f43cc9e..7ad7835 100644
--- a/docs/fuchsia_build_instructions.md
+++ b/docs/fuchsia_build_instructions.md
@@ -86,6 +86,18 @@
$ cd src
```
+### (Linux-only) Install any required host packages
+
+Chromium relies on some platform packages to be present in order to build.
+You can install the current set of required packages with:
+
+```shell
+$ build/install-build-deps.sh
+```
+
+Note that you need to do this only once, and thereafter only if new dependencies
+are added - these will be announced to the chromium-dev@ group.
+
### Update your checkout
To update an existing checkout, you can run
@@ -145,7 +157,24 @@
## Run
-Once it is built, you can run by:
+Once you've built a package, you'll want to run it!
+
+### (Recommended)(Linux-only) Enable KVM acceleration
+
+Under Linux, if your host and target CPU architectures are the same (e.g. you're
+building for Fuchsia/x64 on a Linux/x64 host) then you can benefit from QEMU's
+support for the KVM hypervisor:
+
+1. Install the KVM module for your kernel, to get a /dev/kvm device.
+2. Ensure that your system has a "kvm" group, and it owns /dev/kvm.
+You can do that by installing the QEMU system common package:
+```shell
+$ sudo apt-get install qemu-system-common
+```
+3. Add users to the "kvm" group, and have them login again, to pick-up the new
+group.
+
+### Run test target
```shell
$ out/fuchsia/bin/run_base_unittests
