summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-06-15 13:22:29 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-06-29 13:59:26 (GMT)
commit678f6ee437db04cc8cd3df945a7b5ab5da0b6165 (patch)
tree0b806ea48479866f8714f8826ba7457d897a524c
parent7ce46066a5918df6f1660d4f9cd25a9faabb6493 (diff)
downloadpoky-678f6ee437db04cc8cd3df945a7b5ab5da0b6165.tar.gz
documentation/adt-manual/adt-prepare.xml: 1.1.2 variables and updates
First pass at implementing the poky.ent variables. Also updated text as needed. (From yocto-docs rev: 3472d1c2e7c69e0b544a223204830c0d000033f8) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/adt-manual/adt-prepare.xml76
1 files changed, 34 insertions, 42 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 79c4484..6098fb2 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -1,5 +1,6 @@
1<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 1<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
2"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> 2"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
3[<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
3 4
4<chapter id='adt-prepare'> 5<chapter id='adt-prepare'>
5 6
@@ -56,9 +57,9 @@
56 <para> 57 <para>
57 The ADT Installer is contained in the ADT Installer tarball. 58 The ADT Installer is contained in the ADT Installer tarball.
58 You can download the tarball into any directory from the 59 You can download the tarball into any directory from the
59 <ulink url='http://downloads.yoctoproject.org/releases'>Index of Releases</ulink>, specifically 60 <ulink url='&YOCTO_DL_URL;/releases'>Index of Releases</ulink>, specifically
60 at 61 at
61 <ulink url='http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/adt_installer'></ulink>. 62 <ulink url='&YOCTO_ADTINSTALLER_DL_URL;'></ulink>.
62 Or, you can use BitBake to generate the tarball inside the existing Yocto Project 63 Or, you can use BitBake to generate the tarball inside the existing Yocto Project
63 build tree. 64 build tree.
64 </para> 65 </para>
@@ -81,9 +82,9 @@
81 $ cd ~ 82 $ cd ~
82 $ mkdir yocto-project 83 $ mkdir yocto-project
83 $ cd yocto-project 84 $ cd yocto-project
84 $ wget http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/poky-edison-6.0.1.tar.bz2 85 $ wget &YOCTO_RELEASE_DL_URL;/&YOCTO_POKY_TARBALL;
85 $ tar xjf poky-edison-6.0.1.tar.bz2 86 $ tar xjf &YOCTO_POKY_TARBALL;
86 $ source poky-edison-6.0.1/oe-init-build-env 87 $ source &OE_INIT_PATH;
87 $ bitbake adt-installer 88 $ bitbake adt-installer
88 </literallayout> 89 </literallayout>
89 </para> 90 </para>
@@ -100,7 +101,7 @@
100 a top-level directory named <filename>adt-installer</filename>: 101 a top-level directory named <filename>adt-installer</filename>:
101 <literallayout class='monospaced'> 102 <literallayout class='monospaced'>
102 $ cd ~ 103 $ cd ~
103 $ cp ~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME 104 $ cp ~/poky/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME
104 $ tar -xjf adt_installer.tar.bz2 105 $ tar -xjf adt_installer.tar.bz2
105 </literallayout> 106 </literallayout>
106 Unpacking it creates the directory <filename>adt-installer</filename>, 107 Unpacking it creates the directory <filename>adt-installer</filename>,
@@ -165,20 +166,17 @@
165 166
166 <para> 167 <para>
167 After you have configured the <filename>adt_installer.conf</filename> file, 168 After you have configured the <filename>adt_installer.conf</filename> file,
168 run the installer for this example using the following commands: 169 run the installer using the following command:
169 <literallayout class='monospaced'> 170 <literallayout class='monospaced'>
170 $ cd ~/adt-installer
171 $ ./adt_installer 171 $ ./adt_installer
172 </literallayout> 172 </literallayout>
173 </para> 173 </para>
174 174
175 <note> 175 <note>
176 The ADT Installer requires the <filename>libtool</filename> package to complete. 176 The ADT Installer requires the <filename>libtool</filename> package to complete.
177 If you install the recommended packages as described in the 177 If you install the recommended packages as described in
178 "<ulink url='http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html#packages'>Packages</ulink>" 178 "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>"
179 section of 179 section of The Yocto Project Quick Start, then you will have libtool installed.
180 <ulink url='http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html'>
181 The Yocto Project Quick Start</ulink>, then you will have libtool installed.
182 </note> 180 </note>
183 181
184 <para> 182 <para>
@@ -192,7 +190,7 @@
192 <para> 190 <para>
193 Once the installation completes, the ADT, which includes the cross-toolchain, is installed. 191 Once the installation completes, the ADT, which includes the cross-toolchain, is installed.
194 You will notice environment setup files for the cross-toolchain in 192 You will notice environment setup files for the cross-toolchain in
195 <filename>/opt/poky/1.1.1</filename>, 193 <filename>&YOCTO_ADTPATH_DIR;</filename>,
196 and image tarballs in the <filename>adt-installer</filename> 194 and image tarballs in the <filename>adt-installer</filename>
197 directory according to your installer configurations, and the target sysroot located 195 directory according to your installer configurations, and the target sysroot located
198 according to the <filename>YOCTOADT_TARGET_SYSROOT_LOC_&lt;arch&gt;</filename> variable 196 according to the <filename>YOCTOADT_TARGET_SYSROOT_LOC_&lt;arch&gt;</filename> variable
@@ -215,17 +213,17 @@
215 Follow these steps: 213 Follow these steps:
216 <orderedlist> 214 <orderedlist>
217 <listitem><para>Go to 215 <listitem><para>Go to
218 <ulink url='http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/toolchain'></ulink> 216 <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>
219 and find the folder that matches your host development system 217 and find the folder that matches your host development system
220 (i.e. <filename>i686</filename> for 32-bit machines or 218 (i.e. <filename>i686</filename> for 32-bit machines or
221 <filename>x86_64</filename> for 64-bit machines).</para></listitem> 219 <filename>x86-64</filename> for 64-bit machines).</para></listitem>
222 <listitem><para>Go into that folder and download the toolchain tarball whose name 220 <listitem><para>Go into that folder and download the toolchain tarball whose name
223 includes the appropriate target architecture. 221 includes the appropriate target architecture.
224 For example, if your host development system is an Intel-based 64-bit system and 222 For example, if your host development system is an Intel-based 64-bit system and
225 you are going to use your cross-toolchain for an Intel-based 32-bit target, go into the 223 you are going to use your cross-toolchain for an Intel-based 32-bit target, go into the
226 <filename>x86_64</filename> folder and download the following tarball: 224 <filename>x86_64</filename> folder and download the following tarball:
227 <literallayout class='monospaced'> 225 <literallayout class='monospaced'>
228 poky-eglibc-x86_64-i586-toolchain-1.1.1.tar.bz2 226 poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.tar.bz2
229 </literallayout> 227 </literallayout>
230 <note><para>As an alternative to steps one and two, you can build the toolchain tarball 228 <note><para>As an alternative to steps one and two, you can build the toolchain tarball
231 if you have a Yocto Project build tree. 229 if you have a Yocto Project build tree.
@@ -242,15 +240,9 @@
242 </para></note></para></listitem> 240 </para></note></para></listitem>
243 <listitem><para>Make sure you are in the root directory with root privileges and then expand 241 <listitem><para>Make sure you are in the root directory with root privileges and then expand
244 the tarball. 242 the tarball.
245 The tarball expands into <filename>/opt/poky/1.1.1</filename>. 243 The tarball expands into <filename>&YOCTO_ADTPATH_DIR;</filename>.
246 Once the tarball is expanded, the cross-toolchain is installed. 244 Once the tarball is expanded, the cross-toolchain is installed.
247 You will notice environment setup files for the cross-toolchain in the directory. 245 You will notice environment setup files for the cross-toolchain in the directory.
248 Here is an example where the tarball exists in the user's <filename>Downloads</filename>
249 directory:
250 <literallayout class='monospaced'>
251 # cd /
252 # tar -xjf /home/scottrif/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2
253 </literallayout>
254 </para></listitem> 246 </para></listitem>
255 </orderedlist> 247 </orderedlist>
256 </para> 248 </para>
@@ -287,7 +279,7 @@
287 command.</note></para></listitem> 279 command.</note></para></listitem>
288 <listitem><para>Run <filename>bitbake meta-ide-support</filename> to complete the 280 <listitem><para>Run <filename>bitbake meta-ide-support</filename> to complete the
289 cross-toolchain installation. 281 cross-toolchain installation.
290 <note>If you change out of your working directory after you 282 <note>If change out of your working directory after you
291 <filename>source</filename> the environment setup script and before you run 283 <filename>source</filename> the environment setup script and before you run
292 the <filename>bitbake</filename> command, the command might not work. 284 the <filename>bitbake</filename> command, the command might not work.
293 Be sure to run the <filename>bitbake</filename> command immediately 285 Be sure to run the <filename>bitbake</filename> command immediately
@@ -311,21 +303,21 @@
311 Before you can develop using the cross-toolchain, you need to set up the 303 Before you can develop using the cross-toolchain, you need to set up the
312 cross-development environment by sourcing the toolchain's environment setup script. 304 cross-development environment by sourcing the toolchain's environment setup script.
313 If you used the ADT Installer or used an existing ADT tarball to install the ADT, 305 If you used the ADT Installer or used an existing ADT tarball to install the ADT,
314 then you can find this script in the <filename>/opt/poky/1.1.1</filename> 306 then you can find this script in the <filename>&YOCTO_ADTPATH_DIR;</filename>
315 directory. 307 directory.
316 If you installed the toolchain in the build tree, you can find the environment setup 308 If you installed the toolchain in the build tree, you can find the environment setup
317 script for the toolchain in the Yocto Project build tree's <filename>tmp</filename> directory. 309 script for the toolchain in the Yocto Project build tree's <filename>tmp</filename> directory.
318 </para> 310 </para>
319 311
320 <para> 312 <para>
321 Be sure to source the environment setup script that matches the architecture for 313 Be sure to run the environment setup script that matches the architecture for
322 which you are developing. 314 which you are developing.
323 Environment setup scripts begin with the string “<filename>environment-setup</filename>” 315 Environment setup scripts begin with the string “<filename>environment-setup</filename>”
324 and include as part of their name the architecture. 316 and include as part of their name the architecture.
325 For example, the command to source the toolchain environment setup script 317 For example, the toolchain environment setup script for a 64-bit IA-based architecture would
326 for a 64-bit IA-based machine would be the following: 318 be the following:
327 <literallayout class='monospaced'> 319 <literallayout class='monospaced'>
328 $ source /opt/poky/1.1.1/environment-setup-x86_64-poky-linux 320 &YOCTO_ADTPATH_DIR;/environment-setup-x86_64-poky-linux
329 </literallayout> 321 </literallayout>
330 </para> 322 </para>
331</section> 323</section>
@@ -347,8 +339,8 @@
347 To get the kernel and filesystem images, you either have to build them or download 339 To get the kernel and filesystem images, you either have to build them or download
348 pre-built versions. 340 pre-built versions.
349 You can find examples for both these situations in the 341 You can find examples for both these situations in the
350 "<ulink url='http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html#test-run'>A 342 "<ulink url='&YOCTO_DOCS_QS_URL;#test-run'>A Quick Test Run</ulink>" section of
351 Quick Test Run</ulink>" section of The Yocto Project Quick Start. 343 The Yocto Project Quick Start.
352 </para> 344 </para>
353 345
354 <para> 346 <para>
@@ -357,10 +349,11 @@
357 <filename>mips</filename>, <filename>powerpc</filename>, and <filename>arm</filename>) 349 <filename>mips</filename>, <filename>powerpc</filename>, and <filename>arm</filename>)
358 that you can use unaltered in the QEMU emulator. 350 that you can use unaltered in the QEMU emulator.
359 These kernel images reside in the Yocto Project release 351 These kernel images reside in the Yocto Project release
360 area - <ulink url='http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/machines/'></ulink> 352 area - <ulink url='&YOCTO_MACHINES_DL_URL;'></ulink>
361 and are ideal for experimentation within Yocto Project. 353 and are ideal for experimentation within Yocto Project.
362 For information on the image types you can build using the Yocto Project, see the 354 For information on the image types you can build using the Yocto Project, see the
363 "<ulink url='http://www.yoctoproject.org/docs/1.1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>Reference: Images</ulink>" appendix in The Yocto Project Reference Manual. 355 "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>" appendix in
356 The Yocto Project Reference Manual.
364 </para> 357 </para>
365 358
366 <para> 359 <para>
@@ -391,11 +384,11 @@
391 <listitem><para>Set up the cross-development environment as described in the 384 <listitem><para>Set up the cross-development environment as described in the
392 "<link linkend='setting-up-the-cross-development-environment'>Setting 385 "<link linkend='setting-up-the-cross-development-environment'>Setting
393 Up the Cross-Development Environment</link>" section.</para></listitem> 386 Up the Cross-Development Environment</link>" section.</para></listitem>
394 <listitem><para>Get the <filename>tcf-agent</filename> source code, which is 387 <listitem><para>Get the <filename>tcf-agent</filename> source code using
395 stored using the Subversion SCM, using the following command: 388 the following commands:
396 <literallayout class='monospaced'> 389 <literallayout class='monospaced'>
397 $ svn checkout svn://dev.eclipse.org/svnroot/dsdp/org.eclipse.tm.tcf/trunk/agent \ 390 $ git clone http://git.eclipse.org/gitroot/tcf/org.eclipse.tcf.agent.git
398 &lt;-r #rev_number&gt; 391 $ cd agent
399 </literallayout></para></listitem> 392 </literallayout></para></listitem>
400 <listitem><para>Modify the <filename>Makefile.inc</filename> file 393 <listitem><para>Modify the <filename>Makefile.inc</filename> file
401 for the cross-compilation environment by setting the 394 for the cross-compilation environment by setting the
@@ -432,9 +425,8 @@
432 To extract the root filesystem, first <filename>source</filename> 425 To extract the root filesystem, first <filename>source</filename>
433 the cross-development environment setup script and then 426 the cross-development environment setup script and then
434 use the <filename>runqemu-extract-sdk</filename> command on the 427 use the <filename>runqemu-extract-sdk</filename> command on the
435 filesystem image tarball. 428 filesystem image.
436 For example, the following commands set up the environment by sourcing 429 For example, the following commands set up the environment and then extract
437 the setup script from within the build directory and then extracting
438 the root filesystem from a previously built filesystem image tarball named 430 the root filesystem from a previously built filesystem image tarball named
439 <filename>core-image-sato-sdk-qemux86.tar.bz2</filename>. 431 <filename>core-image-sato-sdk-qemux86.tar.bz2</filename>.
440 The example extracts the root filesystem into the <filename>$HOME/qemux86-sato</filename> 432 The example extracts the root filesystem into the <filename>$HOME/qemux86-sato</filename>