summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-10-25 09:59:53 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-11-01 17:09:53 +0000
commita508060fe4d31ffa4c59c90a751c9d580aa5d064 (patch)
tree3fe472e8973128d278b0edbe55c1015832258851 /documentation/adt-manual
parent853df59bf991aa9dc15b25732291fdc9a01b5c99 (diff)
downloadast2050-yocto-poky-a508060fe4d31ffa4c59c90a751c9d580aa5d064.zip
ast2050-yocto-poky-a508060fe4d31ffa4c59c90a751c9d580aa5d064.tar.gz
adt-manual: Edits to "Optionally Building a Toolchain Installer"
This section pretty much sucked. I did some re-writing and created a list to better present the material and options. (From yocto-docs rev: 4bd833d2a0f55865d9f35784fbfd3c00ebc2daea) 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')
-rw-r--r--documentation/adt-manual/adt-prepare.xml38
1 files changed, 17 insertions, 21 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index b4e27ba..152c7fb 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -582,30 +582,26 @@
<para>
As an alternative to locating and downloading a toolchain installer,
- you can build the toolchain installer if you have a
- <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
- </para>
-
- <para>
- You can build the toolchain
- installer using <filename>bitbake meta-toolchain</filename>.
- This method requires you to still install the target
- sysroot by installing and extracting it separately.
- For information on how to install the sysroot, see the
- "<link linkend='extracting-the-root-filesystem'>Extracting the Root Filesystem</link>" section.
- </para>
-
- <para>
- A final method of building the toolchain installer exists that has
- significant advantages over the previous method.
- This method results in a toolchain installer that contains the sysroot
- that matches your target root filesystem.
- To build this installer, use the
- <filename>bitbake image -c populate_sdk</filename> command.
+ you can build the toolchain installer one of two ways if you have a
+ <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>:
+ <itemizedlist>
+ <listitem><para>Use <filename>bitbake meta-toolchain</filename>.
+ This method requires you to still install the target
+ sysroot by installing and extracting it separately.
+ For information on how to install the sysroot, see the
+ "<link linkend='extracting-the-root-filesystem'>Extracting the Root Filesystem</link>"
+ section.</para></listitem>
+ <listitem><para>Use
+ <filename>bitbake image -c populate_sdk</filename>.
+ This method has significant advantages over the previous method
+ because it results in a toolchain installer that contains the
+ sysroot that matches your target root filesystem.
+ </para></listitem>
+ </itemizedlist>
</para>
<para>
- Remember, before using any <filename>bitbake</filename> command, you
+ Remember, before using any BitBake command, you
must source the build environment setup script
(i.e.
<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>
OpenPOWER on IntegriCloud