summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/adt-manual/adt-prepare.xml17
1 files changed, 9 insertions, 8 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 609c334b0f..3e6b8dad17 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -143,12 +143,13 @@
143 Before running the ADT Installer script, you need to unpack the tarball. 143 Before running the ADT Installer script, you need to unpack the tarball.
144 You can unpack the tarball in any directory you wish. 144 You can unpack the tarball in any directory you wish.
145 Unpacking it creates the directory <filename>adt-installer</filename>, 145 Unpacking it creates the directory <filename>adt-installer</filename>,
146 which contains the ADT Installer script and its configuration file. 146 which contains the ADT Installer script (<filename>adt_installer</filename>)
147 and its configuration file (<filename>adt_installer.conf</filename>).
147 </para> 148 </para>
148 149
149 <para> 150 <para>
150 Before you run the script, however, you should examine the ADT Installer configuration 151 Before you run the script, however, you should examine the ADT Installer configuration
151 file (<filename>adt_installer</filename>) and be sure you are going to get what you want. 152 file and be sure you are going to get what you want.
152 Your configurations determine which kernel and filesystem image are downloaded. 153 Your configurations determine which kernel and filesystem image are downloaded.
153 </para> 154 </para>
154 155
@@ -158,15 +159,15 @@
158 the <filename>adt-installer.conf</filename> file: 159 the <filename>adt-installer.conf</filename> file:
159 160
160 <itemizedlist> 161 <itemizedlist>
161 <listitem><para><filename>YOCTOADT_IPKG_REPO</filename>: This area 162 <listitem><para><filename>YOCTOADT_REPO</filename>: This area
162 includes the IPKG-based packages and the root filesystem upon which 163 includes the IPKG-based packages and the root filesystem upon which
163 the installation is based. 164 the installation is based.
164 If you want to set up your own IPKG repository pointed to by 165 If you want to set up your own IPKG repository pointed to by
165 <filename>YOCTOADT_IPKG_REPO</filename>, you need to be sure that the 166 <filename>YOCTOADT_REPO</filename>, you need to be sure that the
166 directory structure follows the same layout as the reference directory 167 directory structure follows the same layout as the reference directory
167 set up at <ulink url='http://adtrepo.yoctoproject.org'></ulink>. 168 set up at <ulink url='http://adtrepo.yoctoproject.org'></ulink>.
168 Also, your repository needs to be accessible through HTTP.</para></listitem> 169 Also, your repository needs to be accessible through HTTP.</para></listitem>
169 <listitem><para><filename>YOCTOADT-TARGETS</filename>: The machine 170 <listitem><para><filename>YOCTOADT_TARGETS</filename>: The machine
170 target architectures for which you want to set up cross-development 171 target architectures for which you want to set up cross-development
171 environments.</para></listitem> 172 environments.</para></listitem>
172 <listitem><para><filename>YOCTOADT_QEMU</filename>: Indicates whether 173 <listitem><para><filename>YOCTOADT_QEMU</filename>: Indicates whether
@@ -263,15 +264,15 @@
263 <literallayout class='monospaced'> 264 <literallayout class='monospaced'>
264 yocto-eglibc-x86_64-arm-toolchain-gmae-1.1.tar.bz2 265 yocto-eglibc-x86_64-arm-toolchain-gmae-1.1.tar.bz2
265 </literallayout> 266 </literallayout>
266 <note>Alternatively, you can build the toolchain tarball if you have a Yocto 267 <note>As an alternative to steps one and two, you can build the toolchain tarball
267 Project build tree. 268 if you have a Yocto Project build tree.
268 Use the <filename>bitbake meta-toolchain</filename> command after you have 269 Use the <filename>bitbake meta-toolchain</filename> command after you have
269 sourced the <filename>oe-build-init script</filename> located in the Yocto 270 sourced the <filename>oe-build-init script</filename> located in the Yocto
270 Project files. 271 Project files.
271 When the <filename>bitbake</filename> command completes, the toolchain tarball will 272 When the <filename>bitbake</filename> command completes, the toolchain tarball will
272 be in <filename>tmp/deploy/sdk</filename> in the Yocto Project build tree. 273 be in <filename>tmp/deploy/sdk</filename> in the Yocto Project build tree.
273 </note></para></listitem> 274 </note></para></listitem>
274 <listitem><para>Make sure you are in the root directory and then expand 275 <listitem><para>Make sure you are in the root directory with root privileges and then expand
275 the tarball. 276 the tarball.
276 The tarball expands into <filename>/opt/poky/$SDKVERSION</filename>. 277 The tarball expands into <filename>/opt/poky/$SDKVERSION</filename>.
277 Once the tarball in unpacked, the cross-toolchain is installed. 278 Once the tarball in unpacked, the cross-toolchain is installed.