summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual/adt-prepare.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-03-25 11:34:09 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-03-25 17:40:30 +0000
commitafd28598368963dc49bfd02ef2d6f54218d663ae (patch)
tree4902bc1b82b9591d11e22927ac22c15dd20f63c4 /documentation/adt-manual/adt-prepare.xml
parent0cb23cb4247b3969ce8e8d405de431d63fc1b70c (diff)
downloadpoky-afd28598368963dc49bfd02ef2d6f54218d663ae.tar.gz
documentation/adt-manual/adt-prepare.xml: Added instruction for building ADT tarball
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 <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.xml14
1 files changed, 11 insertions, 3 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 77999b8b42..1733141577 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -22,6 +22,14 @@
22 user-space NFS, define which root filesystem profiles to download, 22 user-space NFS, define which root filesystem profiles to download,
23 and allows you to define the target sysroot location. 23 and allows you to define the target sysroot location.
24 </para> 24 </para>
25 <note>
26 If you need to generate the ADT tarball you can do so using the following command:
27 <literallayout class='monospaced'>
28 $ bitbake adt-installer
29 </literallayout>
30 This command generates the file <filename>adt-installer.tar.bz2</filename>
31 in the <filename>../build/tmp/deploy/sdk</filename> directory.
32 </note>
25 33
26 <section id='configuring-and-running-the-adt-installer'> 34 <section id='configuring-and-running-the-adt-installer'>
27 <title>Configuring and Running the ADT Installer</title> 35 <title>Configuring and Running the ADT Installer</title>
@@ -120,14 +128,14 @@
120 <section id='using-an-existing-toolchain-tarball'> 128 <section id='using-an-existing-toolchain-tarball'>
121 <title>Using an Existing Toolchain Tarball</title> 129 <title>Using an Existing Toolchain Tarball</title>
122 <para> 130 <para>
123 If you dont want to use the ADT Installer you can install the toolchain 131 If you do not want to use the ADT Installer you can install the toolchain
124 and the sysroot by hand. 132 and the sysroot by hand.
125 Follow these steps: 133 Follow these steps:
126 <orderedlist> 134 <orderedlist>
127 <listitem><para>Locate and download the architecture-specific toolchain 135 <listitem><para>Locate and download the architecture-specific toolchain
128 tarball from <ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-0.9'></ulink>. 136 tarball from <ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.0'></ulink>.
129 Look in the ‘toolchain’ folder and then open up the folder that matches your 137 Look in the ‘toolchain’ folder and then open up the folder that matches your
130 host development system (i.e. 'i586' for 32-bit machines or 'x86_64' 138 host development system (i.e. 'i686' for 32-bit machines or 'x86_64'
131 for 64-bit machines). 139 for 64-bit machines).
132 Then, select the toolchain tarball whose name includes the appropriate 140 Then, select the toolchain tarball whose name includes the appropriate
133 target architecture. 141 target architecture.