diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index daa1f0efb1..3003f06cd0 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -149,7 +149,7 @@
The Yocto Project team is continually verifying more and more Linux
distributions with each release.
In general, if you have the current release minus one of the following
- distributions you should no problems.
+ distributions you should have no problems.
Ubuntu
Fedora
@@ -278,7 +278,7 @@
Build an image and run it in the QEMU emulator
- Or, use a pre-built image and run it in the QEMU emulator
+ Use a pre-built image and run it in the QEMU emulator
@@ -331,9 +331,8 @@
To help conserve disk space during builds, you can add the following statement
- to your local.conf file in the Yocto Project build
- directory, which for this example
- is edison-6.0-build.
+ to your project's configuration file, which for this example
+ is edison-6.0-build/conf/local.conf.
Adding this statement deletes the work directory used for building a package
once the package is built.
@@ -342,16 +341,15 @@
- The first command retrieves the Yocto Project release tarball from the
- source repositories.
- Notice, the example uses the wget shell command.
+ In the previous example, the first command retrieves the Yocto Project
+ release tarball from the source repositories using the
+ wget command.
Alternatively, you can go to the
- Yocto Project website downloads
- area to retrieve the tarball.
+ Yocto Project website
+ Downloads page to retrieve the tarball.
The second command extracts the files from the tarball and places
them into a directory named poky-edison-6.0 in the current
- directory.
-
+ directory.
The third command runs the Yocto Project environment setup script.
Running this script defines Yocto Project build environment settings needed to
complete the build.
@@ -364,19 +362,18 @@
- Take some time to examine your conf/local.conf file found in the
- Yocto Project build directory.
- The defaults in the local.conf should work fine.
+ Take some time to examine your local.conf file
+ in your project's configuration directory.
+ The defaults in that file should work fine.
However, there are some variables of interest at which you might look.
By default, the target architecture for the build is qemux86,
- which is an image that can be used in the QEMU emulator and is targeted for an
+ which produces an image that can be used in the QEMU emulator and is targeted at an
Intel 32-bit based architecture.
- To change this default, edit the value of the MACHINE variable in the
- conf/local.conf file in the build directory before
- launching the build.
+ To change this default, edit the value of the MACHINE variable
+ in the configuration file before launching the build.
@@ -384,12 +381,12 @@
BB_NUMBER_THREADS and the
PARALLEL_MAKE variables.
By default, these variables are commented out.
- However, if you have a multi-core CPU you might want to remove the comment
- and set the variable
+ However, if you have a multi-core CPU you might want to uncomment
+ the lines and set the variable
BB_NUMBER_THREADS equal to twice the number of your
host's processor cores.
- Also, you could set the variable PARALLEL_MAKE equal to the number
- of processor cores.
+ Also, you could set the variable PARALLEL_MAKE equal to
+ 1.5 times the number of processor cores.
Setting these variables can significantly shorten your build time.
@@ -471,10 +468,10 @@
Installing the Toolchain
You can download the pre-built toolchain, which includes the runqemu
- script and support files, from
- .
+ script and support files, from the appropriate directory under
+ .
Toolchains are available for 32-bit and 64-bit development systems from the
- i686 and x86_64 folders, respectively.
+ i686 and x86_64 directories, respectively.
Each type of development system supports five target architectures.
The tarball files are named such that a string representing the host system appears
first in the filename and then is immediately followed by a string representing
@@ -482,7 +479,7 @@
- yocto-eglibc<host_system>-<arch>-toolchain-gmae-<release>.tar.bz2
+ poky-eglibc<host_system>-<arch>-toolchain-gmae-<release>.tar.bz2
Where:
<host_system> is a string representing your development system:
@@ -500,7 +497,7 @@
- yocto-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2
+ poky-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2
@@ -513,7 +510,7 @@
$ cd /
- $ sudo tar -xvjf ~/toolchains/yocto-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2
+ $ sudo tar -xvjf ~/toolchains/poky-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2
@@ -522,7 +519,7 @@
"Using a Cross-Toolchain Tarball" and
"Using BitBake and the Yocto Project Build Tree" sections in
The Yocto Project
- Application Development Toolkit (ADT) Development Manual.
+ Application Development Toolkit (ADT) User's Guide.
@@ -531,7 +528,7 @@
You can download the pre-built Linux kernel suitable for running in the QEMU emulator from
- .
+ .
Be sure to use the kernel that matches the architecture you want to simulate.
Download areas exist for the five supported machine architectures:
qemuarm, qemumips, qemuppc,
@@ -541,17 +538,12 @@
Most kernel files have one of the following forms:
- *zImage-<kernel-rev>-qemu<arch>-<release>*.bin
- vmlinux-<kernel-rev>-qemu<arch>-<release>*.bin
+ *zImage-qemu<arch>.bin
+ vmlinux-qemu<arch>.bin
Where:
- <kernel-rev> is the base Linux kernel revision
- (e.g. 2.6.37).
-
<arch> is a string representing the target architecture:
x86, x86-64, ppc, mips, or arm.
-
- <release> is the version of Yocto Project.
@@ -568,7 +560,7 @@
You can also download the filesystem image suitable for your target architecture from
- .
+ .
Again, be sure to use the filesystem that matches the architecture you want
to simulate.
@@ -581,19 +573,17 @@
The tar form can be flattened out in your host development system
and used for Yocto Project build purposes.
- yocto-image-<profile>-qemu<arch>-<release>.rootfs.ext3.bz2
- yocto-image-<profile>-qemu<arch>-<release>.rootfs.tar.bz2
+ core-image-<profile>-qemu<arch>.ext3
+ core-image-<profile>-qemu<arch>.tar.bz2
Where:
<profile> is the filesystem image's profile:
- lsb, lsb-dev, lsb-sdk, minimal, minimal-dev, sato, sato-dev, or sato-sdk.
+ lsb, lsb-dev, lsb-sdk, lsb-qt3, minimal, minimal-dev, sato, sato-dev, or sato-sdk.
For information on these types of image profiles, see
Reference: Images in the Yocto Project Reference Manual.
<arch> is a string representing the target architecture:
x86, x86-64, ppc, mips, or arm.
-
- <release> is the version of Yocto Project.
@@ -640,7 +630,7 @@
$ source /opt/poky/1.1/environment-setup-i686-poky-linux
$ runqemu qemux86 bzImage-3.0-qemux86-1.1.bin \
- yocto-image-sato-qemux86-1.1.rootfs.ext3
+ core-image-sato-qemux86.ext3