Update the "getting started".
This reporposes the "simple_build" as a tutorials directory. It isn't
quite as clean as the old tutorial we had in Chrome because most of it is
already written, but this reduces the number of build examples we have
to have.
Bug: 41
Change-Id: Icc234596bf834170440b3af10f7a5b4ef5311591
Reviewed-on: https://gn-review.googlesource.com/c/gn/+/7820
Commit-Queue: Brett Wilson <brettw@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
diff --git a/docs/cross_compiles.md b/docs/cross_compiles.md
index 01de456..ad71b94 100644
--- a/docs/cross_compiles.md
+++ b/docs/cross_compiles.md
@@ -111,10 +111,11 @@
## As a //build/config or //build/toolchain author
-The `default_toolchain` is declared in the `//build/config/BUILDCONFIG.gn`
-file. Usually the `default_toolchain` should be the toolchain for the
-`target_os` and `target_cpu`. The `current_toolchain` reflects the
-toolchain that is currently in effect for a rule.
+The `default_toolchain` is declared in the `BUILDCONFIG.gn` file (in Google
+projects this normally is in the `//build/config` directory). Usually the
+`default_toolchain` should be the toolchain for the `target_os` and
+`target_cpu`. The `current_toolchain` reflects the toolchain that is currently
+in effect for a rule.
Be sure you understand the differences between `host_cpu`, `target_cpu`,
`current_cpu`, and `toolchain_cpu` (and the os equivalents). The first
