diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-10-22 10:28:05 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-10-23 00:03:16 +0100 |
commit | a4266b454cad4cab43de4c6fc823ff2c4e53e5c9 (patch) | |
tree | b633c034053e71259731f8b013dc8a37942fbe6e /documentation/adt-manual/adt-command.xml | |
parent | b1c27ead60765c5ae66257e34ed3f80b8c68e9ed (diff) | |
download | poky-a4266b454cad4cab43de4c6fc823ff2c4e53e5c9.tar.gz |
documentation: adt-manual - final edits before 1.3 lockdown.
Made some minor edits to the book before locking down the
files for 1.3.
(From yocto-docs rev: 2b941103585a31b5dbcb65b784cc3381467ed697)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/adt-manual/adt-command.xml')
-rw-r--r-- | documentation/adt-manual/adt-command.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/adt-manual/adt-command.xml b/documentation/adt-manual/adt-command.xml index 074e51c1f1..4000c924c3 100644 --- a/documentation/adt-manual/adt-command.xml +++ b/documentation/adt-manual/adt-command.xml | |||
@@ -8,9 +8,9 @@ | |||
8 | <para> | 8 | <para> |
9 | Recall that earlier the manual discussed how to use an existing toolchain | 9 | Recall that earlier the manual discussed how to use an existing toolchain |
10 | tarball that had been installed into <filename>/opt/poky</filename>, | 10 | tarball that had been installed into <filename>/opt/poky</filename>, |
11 | which is outside of the build directory | 11 | which is outside of the |
12 | (see the section "<link linkend='using-an-existing-toolchain-tarball'>Using an Existing | 12 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> |
13 | Toolchain Tarball)</link>". | 13 | (see the section "<link linkend='using-an-existing-toolchain-tarball'>Using a Cross-Toolchain Tarball)</link>". |
14 | And, that sourcing your architecture-specific environment setup script | 14 | And, that sourcing your architecture-specific environment setup script |
15 | initializes a suitable cross-toolchain development environment. | 15 | initializes a suitable cross-toolchain development environment. |
16 | During the setup, locations for the compiler, QEMU scripts, QEMU binary, | 16 | During the setup, locations for the compiler, QEMU scripts, QEMU binary, |