summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual/adt-prepare.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-11-07 14:23:56 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-12-03 12:53:06 +0000
commitdd6b2ef9e7a460da329b81ff46f18f2fb657e6bc (patch)
tree0d74b91cb2406017aadcb5ea7d49edf464026551 /documentation/adt-manual/adt-prepare.xml
parent30d7f5263aabffcd068ba3ff3932cba3a2ebef87 (diff)
downloadpoky-dd6b2ef9e7a460da329b81ff46f18f2fb657e6bc.tar.gz
documentation: Scrubbed use of directory names
There was inconsistent use of the way directory names were handled throughout the YP documentation. I have scrubbed the set and replaced many instances such as the following: meta/<something> replaces /meta/<something> poky replaces ~/poky (except in some very specific examples) I basically got rid of leading slash characters. Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> (From yocto-docs rev: ae2e451ed8f61484d04b30017021912c4493a441) 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.xml22
1 files changed, 11 insertions, 11 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 02416b3cda..df9d5b0f76 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -106,7 +106,7 @@
106 build environment while also creating the default 106 build environment while also creating the default
107 Build Directory, and run the BitBake command that 107 Build Directory, and run the BitBake command that
108 results in the tarball 108 results in the tarball
109 <filename>~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>: 109 <filename>poky/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>:
110 <note> 110 <note>
111 Before using BitBake to build the ADT tarball, be 111 Before using BitBake to build the ADT tarball, be
112 sure to make sure your 112 sure to make sure your
@@ -136,7 +136,7 @@
136 a top-level directory named <filename>adt-installer</filename>: 136 a top-level directory named <filename>adt-installer</filename>:
137 <literallayout class='monospaced'> 137 <literallayout class='monospaced'>
138 $ cd ~ 138 $ cd ~
139 $ cp ~/poky/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME 139 $ cp poky/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME
140 $ tar -xjf adt_installer.tar.bz2 140 $ tar -xjf adt_installer.tar.bz2
141 </literallayout> 141 </literallayout>
142 Unpacking it creates the directory <filename>adt-installer</filename>, 142 Unpacking it creates the directory <filename>adt-installer</filename>,
@@ -206,7 +206,7 @@
206 When you run the installer, the environment must use a 206 When you run the installer, the environment must use a
207 host <filename>gcc</filename>: 207 host <filename>gcc</filename>:
208 <literallayout class='monospaced'> 208 <literallayout class='monospaced'>
209 $ cd ~/adt-installer 209 $ cd adt-installer
210 $ ./adt_installer 210 $ ./adt_installer
211 </literallayout> 211 </literallayout>
212 Once the installer begins to run, you are asked to enter the 212 Once the installer begins to run, you are asked to enter the
@@ -303,7 +303,7 @@
303 The first thing the installer prompts you for is the 303 The first thing the installer prompts you for is the
304 directory into which you want to install the toolchain. 304 directory into which you want to install the toolchain.
305 The default directory used is 305 The default directory used is
306 <filename>opt/poky/&DISTRO;</filename>. 306 <filename>/opt/poky/&DISTRO;</filename>.
307 If you do not have write permissions for the directory 307 If you do not have write permissions for the directory
308 into which you are installing the toolchain, the 308 into which you are installing the toolchain, the
309 toolchain installer notifies you and exits. 309 toolchain installer notifies you and exits.
@@ -545,7 +545,7 @@
545 the toolchain environment script in the 545 the toolchain environment script in the
546 <filename>tmp</filename> directory. 546 <filename>tmp</filename> directory.
547 If you installed the toolchain by hand, the environment setup 547 If you installed the toolchain by hand, the environment setup
548 script is located in <filename>opt/poky/&DISTRO;</filename>. 548 script is located in <filename>/opt/poky/&DISTRO;</filename>.
549 </para> 549 </para>
550 550
551 <para> 551 <para>
@@ -563,16 +563,16 @@
563 built filesystem that is located in the 563 built filesystem that is located in the
564 <filename>~/Downloads</filename> directory. 564 <filename>~/Downloads</filename> directory.
565 Furthermore, this command extracts the root filesystem into the 565 Furthermore, this command extracts the root filesystem into the
566 <filename>$HOME/qemux86-sato</filename> directory: 566 <filename>qemux86-sato</filename> directory:
567 <literallayout class='monospaced'> 567 <literallayout class='monospaced'>
568 $ cd ~ 568 $ cd ~
569 $ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux 569 $ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux
570 $ runqemu-extract-sdk \ 570 $ runqemu-extract-sdk \
571 ~Downloads/core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2 \ 571 ~/Downloads/core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2 \
572 $HOME/qemux86-sato 572 $HOME/qemux86-sato
573 </literallayout> 573 </literallayout>
574 You could now point to the target sysroot at 574 You could now point to the target sysroot at
575 <filename>$HOME/qemux86-sato</filename>. 575 <filename>qemux86-sato</filename>.
576 </para> 576 </para>
577 </section> 577 </section>
578</section> 578</section>
@@ -625,13 +625,13 @@
625 <note> 625 <note>
626 By default, this toolchain does not build static binaries. 626 By default, this toolchain does not build static binaries.
627 If you want to use the toolchain to build these types of libraries, 627 If you want to use the toolchain to build these types of libraries,
628 you need to be sure your image has the appropriate static 628 you need to be sure your image has the appropriate static
629 development libraries. 629 development libraries.
630 Use the 630 Use the
631 <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink> 631 <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink>
632 variable inside your <filename>local.conf</filename> file to 632 variable inside your <filename>local.conf</filename> file to
633 install the appropriate library packages. 633 install the appropriate library packages.
634 Following is an example using <filename>eglibc</filename> static 634 Following is an example using <filename>eglibc</filename> static
635 development libraries: 635 development libraries:
636 <literallayout class='monospaced'> 636 <literallayout class='monospaced'>
637 IMAGE_INSTALL_append = " eglibc-staticdev" 637 IMAGE_INSTALL_append = " eglibc-staticdev"