diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2011-09-01 09:18:33 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-09-02 23:38:51 +0100 |
commit | 77d1ba446c153afbe9fde7fcfa7afdd734104f9e (patch) | |
tree | f771e2243359e0e3814cef22dd220d1a4d01c70b /documentation/adt-manual/adt-command.xml | |
parent | b214cdc7e8105c59c806042d5d994216de409025 (diff) | |
download | poky-77d1ba446c153afbe9fde7fcfa7afdd734104f9e.tar.gz |
documentation/adt-manual: General edits.
I made a pass through the manual and made some general formatting changes,
updated some links in anticipation for the 1.1 release.
(From yocto-docs rev: f2d3a012fbe4e8db3cf07e5497acfdf732e55d97)
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 | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/documentation/adt-manual/adt-command.xml b/documentation/adt-manual/adt-command.xml index e647a374a8..96b779c3b7 100644 --- a/documentation/adt-manual/adt-command.xml +++ b/documentation/adt-manual/adt-command.xml | |||
@@ -3,12 +3,13 @@ | |||
3 | 3 | ||
4 | <chapter id='using-the-command-line'> | 4 | <chapter id='using-the-command-line'> |
5 | <title>Using the Command Line</title> | 5 | <title>Using the Command Line</title> |
6 | |||
6 | <para> | 7 | <para> |
7 | Recall that earlier we talked about how to use an existing toolchain | 8 | Recall that earlier the manual discussed how to use an existing toolchain |
8 | tarball that had been installed into <filename>/opt/poky</filename>, | 9 | tarball that had been installed into <filename>/opt/poky</filename>, |
9 | which is outside of the Yocto Project build tree | 10 | which is outside of the Yocto Project build tree |
10 | (see <xref linkend='using-an-existing-toolchain-tarball'> | 11 | (see the section "<link linkend='using-an-existing-toolchain-tarball'>Using an Existing |
11 | Using an Existing Toolchain Tarball)</xref>. | 12 | Toolchain Tarball)</link>". |
12 | And, that sourcing your architecture-specific environment setup script | 13 | And, that sourcing your architecture-specific environment setup script |
13 | initializes a suitable cross-toolchain development environment. | 14 | initializes a suitable cross-toolchain development environment. |
14 | This setup occurs by adding the compiler, QEMU scripts, QEMU binary, | 15 | This setup occurs by adding the compiler, QEMU scripts, QEMU binary, |
@@ -20,11 +21,12 @@ | |||
20 | test results for tests that need target hardware on which to run. | 21 | test results for tests that need target hardware on which to run. |
21 | These conditions allow you to easily use the toolchain outside of the | 22 | These conditions allow you to easily use the toolchain outside of the |
22 | Yocto Project build environment on both autotools-based projects and | 23 | Yocto Project build environment on both autotools-based projects and |
23 | makefile-based projects. | 24 | Makefile-based projects. |
24 | </para> | 25 | </para> |
25 | 26 | ||
26 | <section id='autotools-based-projects'> | 27 | <section id='autotools-based-projects'> |
27 | <title>Autotools-Based Projects</title> | 28 | <title>Autotools-Based Projects</title> |
29 | |||
28 | <para> | 30 | <para> |
29 | For an autotools-based project, you can use the cross-toolchain by just | 31 | For an autotools-based project, you can use the cross-toolchain by just |
30 | passing the appropriate host option to <filename>configure.sh</filename>. | 32 | passing the appropriate host option to <filename>configure.sh</filename>. |
@@ -49,8 +51,9 @@ | |||
49 | 51 | ||
50 | <section id='makefile-based-projects'> | 52 | <section id='makefile-based-projects'> |
51 | <title>Makefile-Based Projects</title> | 53 | <title>Makefile-Based Projects</title> |
54 | |||
52 | <para> | 55 | <para> |
53 | For a makefile-based project you use the cross-toolchain by making sure | 56 | For a Makefile-based project, you use the cross-toolchain by making sure |
54 | the tools are used. | 57 | the tools are used. |
55 | You can do this as follows: | 58 | You can do this as follows: |
56 | <literallayout class='monospaced'> | 59 | <literallayout class='monospaced'> |