summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-09-14 20:04:42 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-09-24 15:36:05 (GMT)
commit7bff7a05c63b1c25b7488afcd64a4e83d491f0a7 (patch)
treed2d4955a5aca6c58e28ea011ec4f0e4419cc407a
parent21ce4e481ee812aa17ba5a08b327d91fa241c4c5 (diff)
downloadpoky-7bff7a05c63b1c25b7488afcd64a4e83d491f0a7.tar.gz
documentation/yocto-project-qs/yocto-project-qs.xml: Minor corrections
A few minor corrections to fix some wordings. (From yocto-docs rev: de71001992150da685a70389e28313df609d6521) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml20
1 files changed, 11 insertions, 9 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index 3fde5b7..9800338 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -537,9 +537,9 @@
537 Toolchains are available for 32-bit and 64-bit development systems from the 537 Toolchains are available for 32-bit and 64-bit development systems from the
538 <filename>i686</filename> and <filename>x86-64</filename> directories, respectively. 538 <filename>i686</filename> and <filename>x86-64</filename> directories, respectively.
539 Each type of development system supports five target architectures. 539 Each type of development system supports five target architectures.
540 The names of the tarballs are such that a string representing the host system appears 540 The names of the tarball installer scripts are such that a string representing the
541 first in the filename and then is immediately followed by a string representing 541 host system appears first in the filename and then is immediately followed by a
542 the target architecture. 542 string representing the target architecture.
543 </para> 543 </para>
544 544
545 <literallayout class='monospaced'> 545 <literallayout class='monospaced'>
@@ -735,7 +735,7 @@
735 pages. 735 pages.
736 </para> 736 </para>
737 </footnote> 737 </footnote>
738 gives you a very fast description of how to use the Yocto Project to build images 738 gives you a minimal description of how to use the Yocto Project to build images
739 for a BeagleBoard xM starting from scratch. 739 for a BeagleBoard xM starting from scratch.
740 The steps were performed on a 64-bit Ubuntu 10.04 system. 740 The steps were performed on a 64-bit Ubuntu 10.04 system.
741 </para> 741 </para>
@@ -777,16 +777,18 @@
777 <title>Initializing the Build Environment</title> 777 <title>Initializing the Build Environment</title>
778 778
779 <para> 779 <para>
780 From the parent directory of local source directory, initialize your environment 780 From the parent directory your
781 and provide a meaningful 781 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>,
782 initialize your environment and provide a meaningful
782 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink> 783 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink>
783 name: 784 name:
784 <literallayout class='monospaced'> 785 <literallayout class='monospaced'>
785 $ source poky/oe-init-build-env mybuilds 786 $ source poky/&OE_INIT_FILE; mybuilds
786 </literallayout> 787 </literallayout>
787 At this point, the <filename>mybuilds</filename> directory has been created for you 788 At this point, the <filename>mybuilds</filename> directory has been created for you
788 and it is now your current working directory. 789 and it is now your current working directory.
789 If you don't provide your own directory name it defaults to <filename>build</filename>. 790 If you don't provide your own directory name it defaults to <filename>build</filename>,
791 which is inside the source directory.
790 </para> 792 </para>
791 </section> 793 </section>
792 794
@@ -851,7 +853,7 @@
851 $ bitbake -c fetchall core-image-minimal 853 $ bitbake -c fetchall core-image-minimal
852 </literallayout> 854 </literallayout>
853 This variation guarantees that you have all the sources for that BitBake target 855 This variation guarantees that you have all the sources for that BitBake target
854 should you to disconnect from the net and want to do the build later offline. 856 should you disconnect from the net and want to do the build later offline.
855 </para></listitem> 857 </para></listitem>
856 <listitem><para>Specify to continue the build even if BitBake encounters an error. 858 <listitem><para>Specify to continue the build even if BitBake encounters an error.
857 By default, BitBake aborts the build when it encounters an error. 859 By default, BitBake aborts the build when it encounters an error.