summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-04-17 00:23:51 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-17 21:34:22 (GMT)
commit92243fa59b65d7f1f8db564d2c5aa2062fe7b5b7 (patch)
tree69bae89bd359528e3b2c1e20307a93a7cc748d1e /documentation/adt-manual
parentc29c155b7f0ed442199b1a045a18e7141c4d2d37 (diff)
downloadpoky-92243fa59b65d7f1f8db564d2c5aa2062fe7b5b7.tar.gz
adt-manual: Minor edits and links.
(From yocto-docs rev: f2ceeef22a357a4c8a5fa920fd03c57b8e017200) 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')
-rw-r--r--documentation/adt-manual/adt-prepare.xml24
1 files changed, 12 insertions, 12 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 4df10bf..c6bfd49 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -91,16 +91,16 @@
91 <para> 91 <para>
92 If you use BitBake to generate the ADT Installer tarball, you must 92 If you use BitBake to generate the ADT Installer tarball, you must
93 <filename>source</filename> the environment setup script 93 <filename>source</filename> the environment setup script
94 (<filename>&OE_INIT_FILE;</filename>) located 94 (<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>)
95 in the Source Directory before running the <filename>bitbake</filename> 95 located in the Source Directory before running the
96 command that creates the tarball. 96 BitBake command that creates the tarball.
97 </para> 97 </para>
98 98
99 <para> 99 <para>
100 The following example commands download the Poky tarball, set up the 100 The following example commands download the Poky tarball, set up the
101 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>, 101 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>,
102 set up the environment while also creating the default Build Directory, 102 set up the environment while also creating the default Build Directory,
103 and run the <filename>bitbake</filename> command that results in the tarball 103 and run the BitBake command that results in the tarball
104 <filename>~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>: 104 <filename>~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>:
105 <literallayout class='monospaced'> 105 <literallayout class='monospaced'>
106 $ cd ~ 106 $ cd ~
@@ -293,7 +293,7 @@
293 variable is correctly set if you are building 293 variable is correctly set if you are building
294 a toolchain for an architecture that differs from your 294 a toolchain for an architecture that differs from your
295 current development host machine.</para> 295 current development host machine.</para>
296 <para>When the <filename>bitbake</filename> command 296 <para>When the BitBake command
297 completes, the toolchain installer will be in 297 completes, the toolchain installer will be in
298 <filename>tmp/deploy/sdk</filename> in the Build 298 <filename>tmp/deploy/sdk</filename> in the Build
299 Directory.</para> 299 Directory.</para>
@@ -326,7 +326,7 @@
326 A final way of making the cross-toolchain available is to use BitBake 326 A final way of making the cross-toolchain available is to use BitBake
327 to generate the toolchain within an existing 327 to generate the toolchain within an existing
328 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. 328 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
329 This method does not install the toolchain into the 329 This method does not install the toolchain into the default
330 <filename>/opt</filename> directory. 330 <filename>/opt</filename> directory.
331 As with the previous method, if you need to install the target sysroot, you must 331 As with the previous method, if you need to install the target sysroot, you must
332 do that separately as well. 332 do that separately as well.
@@ -355,11 +355,11 @@
355 cross-toolchain generation. 355 cross-toolchain generation.
356 <note>If you change out of your working directory after you 356 <note>If you change out of your working directory after you
357 <filename>source</filename> the environment setup script and before you run 357 <filename>source</filename> the environment setup script and before you run
358 the <filename>bitbake</filename> command, the command might not work. 358 the BitBake command, the command might not work.
359 Be sure to run the <filename>bitbake</filename> command immediately 359 Be sure to run the BitBake command immediately
360 after checking or editing the <filename>local.conf</filename> but without 360 after checking or editing the <filename>local.conf</filename> but without
361 changing out of your working directory.</note> 361 changing out of your working directory.</note>
362 Once the <filename>bitbake</filename> command finishes, 362 Once the BitBake command finishes,
363 the cross-toolchain is generated and populated within the Build Directory. 363 the cross-toolchain is generated and populated within the Build Directory.
364 You will notice environment setup files for the cross-toolchain in the 364 You will notice environment setup files for the cross-toolchain in the
365 Build Directory in the <filename>tmp</filename> directory. 365 Build Directory in the <filename>tmp</filename> directory.
@@ -393,7 +393,7 @@
393 <para> 393 <para>
394 Be sure to run the environment setup script that matches the architecture for 394 Be sure to run the environment setup script that matches the architecture for
395 which you are developing. 395 which you are developing.
396 Environment setup scripts begin with the string <filename>environment-setup</filename> 396 Environment setup scripts begin with the string "<filename>environment-setup</filename>"
397 and include as part of their name the architecture. 397 and include as part of their name the architecture.
398 For example, the toolchain environment setup script for a 64-bit 398 For example, the toolchain environment setup script for a 64-bit
399 IA-based architecture installed in the default installation directory 399 IA-based architecture installed in the default installation directory
@@ -442,8 +442,8 @@
442 <para> 442 <para>
443 If you are planning on developing against your image and you are not 443 If you are planning on developing against your image and you are not
444 building or using one of the Yocto Project development images 444 building or using one of the Yocto Project development images
445 (e.g. core-image-*-dev), you must be sure to include the development 445 (e.g. <filename>core-image-*-dev</filename>), you must be sure to
446 packages as part of your image recipe. 446 include the development packages as part of your image recipe.
447 </para> 447 </para>
448 448
449 <para> 449 <para>