diff options
authorScott Rifenbark <>2011-03-25 11:34:09 -0600
committerRichard Purdie <>2011-03-25 17:40:53 +0000
commit8b6416db1e04af83ecdf57522240ac859d5d8031 (patch)
parent17600d23d8edfe01bd4512ad8e13f22c79f79140 (diff)
documentation/adt-manual/adt-prepare.xml: Added instruction for building ADT tarballbernard-5.0
I added a note in the "Installing the ADT" section (2.1) saying that if you need to build the ADT tarball you can use 'bitbake adt-installer'. I also changed the location of the toolchain from '...yocto-0.9' to '...yocto-1.0'. Finally, I changed the host sub-directory in the toolchain directory from 'i586' to i686'. (From OE-Core rev: 18124c5065fc570e672d068e915e0f476d20379c) Signed-off-by: Scott Rifenbark <> Signed-off-by: Richard Purdie <>
1 files changed, 11 insertions, 3 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 77999b8..1733141 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -22,6 +22,14 @@
user-space NFS, define which root filesystem profiles to download,
and allows you to define the target sysroot location.
+ <note>
+ If you need to generate the ADT tarball you can do so using the following command:
+ <literallayout class='monospaced'>
+ $ bitbake adt-installer
+ </literallayout>
+ This command generates the file <filename>adt-installer.tar.bz2</filename>
+ in the <filename>../build/tmp/deploy/sdk</filename> directory.
+ </note>
<section id='configuring-and-running-the-adt-installer'>
<title>Configuring and Running the ADT Installer</title>
@@ -120,14 +128,14 @@
<section id='using-an-existing-toolchain-tarball'>
<title>Using an Existing Toolchain Tarball</title>
- If you don’t want to use the ADT Installer you can install the toolchain
+ If you do not want to use the ADT Installer you can install the toolchain
and the sysroot by hand.
Follow these steps:
<listitem><para>Locate and download the architecture-specific toolchain
- tarball from <ulink url=''></ulink>.
+ tarball from <ulink url=''></ulink>.
Look in the ‘toolchain’ folder and then open up the folder that matches your
- host development system (i.e. 'i586' for 32-bit machines or 'x86_64'
+ host development system (i.e. 'i686' for 32-bit machines or 'x86_64'
for 64-bit machines).
Then, select the toolchain tarball whose name includes the appropriate
target architecture.