summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual/adt-prepare.xml
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/adt-prepare.xml
parent853df59bf991aa9dc15b25732291fdc9a01b5c99 (diff)
downloadpoky-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/adt-prepare.xml')
-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 b4e27baf6f..152c7fbfa6 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -582,30 +582,26 @@
582 582
583 <para> 583 <para>
584 As an alternative to locating and downloading a toolchain installer, 584 As an alternative to locating and downloading a toolchain installer,
585 you can build the toolchain installer if you have a 585 you can build the toolchain installer one of two ways if you have a
586 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. 586 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>:
587 </para> 587 <itemizedlist>
588 588 <listitem><para>Use <filename>bitbake meta-toolchain</filename>.
589 <para> 589 This method requires you to still install the target
590 You can build the toolchain 590 sysroot by installing and extracting it separately.
591 installer using <filename>bitbake meta-toolchain</filename>. 591 For information on how to install the sysroot, see the
592 This method requires you to still install the target 592 "<link linkend='extracting-the-root-filesystem'>Extracting the Root Filesystem</link>"
593 sysroot by installing and extracting it separately. 593 section.</para></listitem>
594 For information on how to install the sysroot, see the 594 <listitem><para>Use
595 "<link linkend='extracting-the-root-filesystem'>Extracting the Root Filesystem</link>" section. 595 <filename>bitbake image -c populate_sdk</filename>.
596 </para> 596 This method has significant advantages over the previous method
597 597 because it results in a toolchain installer that contains the
598 <para> 598 sysroot that matches your target root filesystem.
599 A final method of building the toolchain installer exists that has 599 </para></listitem>
600 significant advantages over the previous method. 600 </itemizedlist>
601 This method results in a toolchain installer that contains the sysroot
602 that matches your target root filesystem.
603 To build this installer, use the
604 <filename>bitbake image -c populate_sdk</filename> command.
605 </para> 601 </para>
606 602
607 <para> 603 <para>
608 Remember, before using any <filename>bitbake</filename> command, you 604 Remember, before using any BitBake command, you
609 must source the build environment setup script 605 must source the build environment setup script
610 (i.e. 606 (i.e.
611 <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> 607 <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>