|author||Scott Rifenbark <firstname.lastname@example.org>||2012-09-14 13:04:42 -0700|
|committer||Richard Purdie <email@example.com>||2012-09-24 16:36:05 +0100|
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 <firstname.lastname@example.org> Signed-off-by: Richard Purdie <email@example.com>
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 3fde5b7d08..9800338e90 100644
@@ -537,9 +537,9 @@
Toolchains are available for 32-bit and 64-bit development systems from the
<filename>i686</filename> and <filename>x86-64</filename> directories, respectively.
Each type of development system supports five target architectures.
- The names of the tarballs are such that a string representing the host system appears
- first in the filename and then is immediately followed by a string representing
- the target architecture.
+ The names of the tarball installer scripts are such that a string representing the
+ host system appears first in the filename and then is immediately followed by a
+ string representing the target architecture.
@@ -735,7 +735,7 @@
- gives you a very fast description of how to use the Yocto Project to build images
+ gives you a minimal description of how to use the Yocto Project to build images
for a BeagleBoard xM starting from scratch.
The steps were performed on a 64-bit Ubuntu 10.04 system.
@@ -777,16 +777,18 @@
<title>Initializing the Build Environment</title>
- From the parent directory of local source directory, initialize your environment
- and provide a meaningful
+ From the parent directory your
+ <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>,
+ initialize your environment and provide a meaningful
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink>
- $ source poky/oe-init-build-env mybuilds
+ $ source poky/&OE_INIT_FILE; mybuilds
At this point, the <filename>mybuilds</filename> directory has been created for you
and it is now your current working directory.
- If you don't provide your own directory name it defaults to <filename>build</filename>.
+ If you don't provide your own directory name it defaults to <filename>build</filename>,
+ which is inside the source directory.
@@ -851,7 +853,7 @@
$ bitbake -c fetchall core-image-minimal
This variation guarantees that you have all the sources for that BitBake target
- should you to disconnect from the net and want to do the build later offline.
+ should you disconnect from the net and want to do the build later offline.
<listitem><para>Specify to continue the build even if BitBake encounters an error.
By default, BitBake aborts the build when it encounters an error.