summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-10-25 10:37:12 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-11-01 17:09:54 +0000
commit195266be3421e9c695f84d37a040870c1bcd0791 (patch)
treeabc335be0b1db514ee018727c48b75e7989f3ea9
parenta508060fe4d31ffa4c59c90a751c9d580aa5d064 (diff)
downloadpoky-195266be3421e9c695f84d37a040870c1bcd0791.tar.gz
adt-manual: Minor edits to Chapter 4
Broke up the introductory paragraph a bit because it was one large chunk of text. Added the release variable to specify the directory in which to find the environment setup script for the toolchain. (From yocto-docs rev: 82f4a35fa29526fcfa4041c410b52f9c87ec939a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/adt-manual/adt-command.xml29
1 files changed, 19 insertions, 10 deletions
diff --git a/documentation/adt-manual/adt-command.xml b/documentation/adt-manual/adt-command.xml
index be54ae8ec3..0ed3396ef5 100644
--- a/documentation/adt-manual/adt-command.xml
+++ b/documentation/adt-manual/adt-command.xml
@@ -8,23 +8,32 @@
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 the default installation 10 tarball that had been installed into the default installation
11 directory, <filename>/opt/poky</filename>, which is outside of the 11 directory, <filename>/opt/poky/&DISTRO;</filename>, which is outside of the
12 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> 12 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
13 (see the section "<link linkend='using-an-existing-toolchain-tarball'>Using a Cross-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 </para>
17
18 <para>
19 During this setup, locations for the compiler, QEMU scripts, QEMU binary,
17 a special version of <filename>pkgconfig</filename> and other useful 20 a special version of <filename>pkgconfig</filename> and other useful
18 utilities are added to the <filename>PATH</filename> variable. 21 utilities are added to the <filename>PATH</filename> variable.
19 Variables to assist <filename>pkgconfig</filename> and <filename>autotools</filename> 22 Also, variables to assist
20 are also defined so that, 23 <filename>pkgconfig</filename> and <filename>autotools</filename>
21 for example, <filename>configure.sh</filename> can find pre-generated 24 are also defined so that, for example, <filename>configure.sh</filename>
22 test results for tests that need target hardware on which to run. 25 can find pre-generated test results for tests that need target hardware
23 These conditions allow you to easily use the toolchain outside of the 26 on which to run.
24 OpenEmbedded build environment on both autotools-based projects and
25 Makefile-based projects.
26 </para> 27 </para>
27 28
29 <para>
30 Collectively, these conditions allow you to easily use the toolchain
31 outside of the OpenEmbedded build environment on both autotools-based
32 projects and Makefile-based projects.
33 This chapter provides information for both these types of projects.
34 </para>
35
36
28<section id='autotools-based-projects'> 37<section id='autotools-based-projects'>
29<title>Autotools-Based Projects</title> 38<title>Autotools-Based Projects</title>
30 39
@@ -179,7 +188,7 @@
179 If <filename>configure</filename> script results in problems recognizing the 188 If <filename>configure</filename> script results in problems recognizing the
180 <filename>--with-libtool-sysroot=&lt;sysroot-dir&gt;</filename> option, 189 <filename>--with-libtool-sysroot=&lt;sysroot-dir&gt;</filename> option,
181 regenerate the script to enable the support by doing the following and then 190 regenerate the script to enable the support by doing the following and then
182 re-running the script: 191 run the script again:
183 <literallayout class='monospaced'> 192 <literallayout class='monospaced'>
184 $ libtoolize --automake 193 $ libtoolize --automake
185 $ aclocal -I ${OECORE_NATIVE_SYSROOT}/usr/share/aclocal \ 194 $ aclocal -I ${OECORE_NATIVE_SYSROOT}/usr/share/aclocal \