From c7dffc7af14a46180c9e79fc8091eac8d9831952 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 19 Aug 2014 10:22:48 +0300 Subject: yocto-project-qs: Minor edits from a read-thru * Added some text associated with the screencast we link to that calls out the fact that the screencast is somewhat dated but still useful. * Replaced all user input in examples so that they are formatted using the tags. * Fixed a few places so that they use better and clearer wording. (From yocto-docs rev: f99536a7581ef9b8b57a446b65e4ebb902b4e4b1) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../yocto-project-qs/yocto-project-qs.xml | 59 ++++++++++++---------- 1 file changed, 31 insertions(+), 28 deletions(-) (limited to 'documentation/yocto-project-qs') diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index 333ccc4727..7a083bc064 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml @@ -86,10 +86,12 @@ the Yocto Project Reference Manual. Developer Screencast: The - Getting Started with the Yocto Project - New - Developer Screencast Tutorial provides a 30-minute video - created for users unfamiliar with the Yocto Project but familiar - with Linux build systems. + Getting Started with the Yocto Project - New Developer Screencast Tutorial + provides a 30-minute video created for users unfamiliar with + the Yocto Project but familiar with Linux build systems. + While this screencast is somewhat dated, the introductory + and fundamental concepts are useful for the beginner. + @@ -177,7 +179,8 @@ decrease the time needed to build images. - The right packages. + Appropriate packages installed on the system you are using for + builds. A release of the Yocto Project. @@ -509,7 +512,7 @@ Another couple of variables of interest are the BB_NUMBER_THREADS and the PARALLEL_MAKE variables. - By default, these variables are set to how ever many processor + By default, these variables are set to the number of processor cores your build host uses. However, if your build host uses multiple processor cores, you should increase these settings to twice the number of @@ -546,7 +549,7 @@ "Required Git, tar, and Python" section in the Yocto Project Reference Manual. - The final command runs the image: + The final command runs the image using the QEMU emulator: $ runqemu qemux86 @@ -622,25 +625,25 @@ - poky-eglibc-<host_system>-<image_type>-<arch>-toolchain-<release_version>.sh + poky-eglibc-host_system-image_type-arch-toolchain-release_version.sh Where: - <host_system> is a string representing your development system: + host_system is a string representing your development system: i686 or x86_64. - <image_type> is a string representing the image you wish to + image_type is a string representing the image you wish to develop a Software Development Toolkit (SDK) for use against. The Yocto Project builds toolchain installers using the following BitBake command: bitbake core-image-sato -c populate_sdk - <arch> is a string representing the tuned target architecture: + arch is a string representing the tuned target architecture: i586, x86_64, powerpc, mips, armv7a or armv5te - <release_version> is a string representing the release number of the + release_version is a string representing the release number of the Yocto Project: &DISTRO;, &DISTRO;+snapshot @@ -706,11 +709,11 @@ Most kernel files have one of the following forms: - *zImage-qemu<arch>.bin - vmlinux-qemu<arch>.bin + *zImage-qemuarch.bin + vmlinux-qemuarch.bin Where: - <arch> is a string representing the target architecture: + arch is a string representing the target architecture: x86, x86-64, ppc, mips, or arm. @@ -740,17 +743,17 @@ The tar form can be flattened out in your host development system and used for build purposes with the Yocto Project. - core-image-<profile>-qemu<arch>.ext3 - core-image-<profile>-qemu<arch>.tar.bz2 + core-image-profile-qemuarch.ext3 + core-image-profile-qemuarch.tar.bz2 Where: - <profile> is the filesystem image's profile: + profile is the filesystem image's profile: 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 the "Images" chapter in the Yocto Project - Reference Manual. + profiles, see the "Images" + chapter in the Yocto Project Reference Manual. - <arch> is a string representing the target architecture: + arch is a string representing the target architecture: x86, x86-64, ppc, mips, or arm. @@ -763,13 +766,13 @@ Before you start the QEMU emulator, you need to set up the emulation environment. The following command form sets up the emulation environment. - $ source &YOCTO_ADTPATH_DIR;/environment-setup-<arch>-poky-linux-<if> + $ source &YOCTO_ADTPATH_DIR;/environment-setup-arch-poky-linux-if Where: - <arch> is a string representing the target architecture: + arch is a string representing the target architecture: i586, x86_64, ppc603e, mips, or armv5te. - <if> is a string representing an embedded application binary interface. + if is a string representing an embedded application binary interface. Not all setup scripts include this string. @@ -777,15 +780,15 @@ Finally, this command form invokes the QEMU emulator - $ runqemu <qemuarch> <kernel-image> <filesystem-image> + $ runqemu qemuarch kernel-image filesystem-image Where: - <qemuarch> is a string representing the target architecture: qemux86, qemux86-64, + qemuarch is a string representing the target architecture: qemux86, qemux86-64, qemuppc, qemumips, or qemuarm. - <kernel-image> is the architecture-specific kernel image. + kernel-image is the architecture-specific kernel image. - <filesystem-image> is the .ext3 filesystem image. + filesystem-image is the .ext3 filesystem image. -- cgit 1.2.3-korg