developer_guide: Address style issues and format
Address format issues raised in crrev.com/c/3401856
after submission: add missing blank line after note
element and move new note from popout block to side
notes.
BUG=None
TEST=Preview
Change-Id: I0ad0d64cc8183f3661696f51c07263bbb6fa7e6b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/docs/+/3437025
Tested-by: Cristina Guerrero <crisguerrero@chromium.org>
Auto-Submit: Cristina Guerrero <crisguerrero@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
diff --git a/developer_guide.md b/developer_guide.md
index 530ebdc..cf36bc6 100644
--- a/developer_guide.md
+++ b/developer_guide.md
@@ -438,6 +438,7 @@
use features that access Google APIs (**signing in**, translating web pages,
geolocation, etc).
***
+
You will need to have keys (see [API Keys]) either in your include.gypi, or in a
file in your home directory called ".googleapikeys". If either of these file are
present for step 1 of building (below) they will be included automatically. If
@@ -691,21 +692,6 @@
(inside) ./build_packages --board=${BOARD}
```
-*** note
-**Note for Googlers:**
-`./build_packages` is generally enough to include Chrome in your image if you
-have included the internal manifest when initializing the repo. However, there
-may be some cases where the build produces Chromium instead. Running the command
-again including the flags `--internal` and `--nouse_any_chrome` guarantees Chrome
-is included in the build. `--nouse_any_chrome` creates a fresh build of
-Chromium/Chrome instead of reusing an existing prebuilt, making the build
-process slower.
-
-```bash
-(inside) ./build_packages --board=${BOARD} --internal --nouse_any_chrome
-```
-***
-
This step is the rough equivalent of `make all` in a standard Makefile
system. This command handles incremental builds; you should run it whenever you
change something and need to rebuild it (or after you run `repo sync`).
@@ -724,6 +710,13 @@
these options will temporarily switch to `performance` for faster builds.
`--autosetgov_sticky` makes `build_packages` remember to always use
`--autosetgov`.
+* (For Googlers) `./build_packages` is generally enough to include Chrome in
+ your image if you have included the internal manifest when initializing the
+ repo. However, there may be some cases where the build produces Chromium
+ instead. Running the command again including the flags `--internal` and
+ `--nouse_any_chrome` guarantees Chrome is included in the build.
+ `--nouse_any_chrome` creates a fresh build of Chromium/Chrome instead of
+ reusing an existing prebuilt, making the build process slower.
* Like `setup_board`, `build_packages` also calls `update_chroot`, which will
update the toolchain if `repo sync` has been run and the toolchain is
out of date.