From 27e2d19e6dbe2b3752ed2d81ae191b7f391ab8b2 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 22 Oct 2010 08:36:29 -0700 Subject: Updated the yocto-environment picture and added example command edits. When scaled to fit the page the picture had a black vertical line artifact to the right. I snipped out the image a little tigher to eliminate this line. I also incorporated Dirk's comments tightening up the sequence of example commands to do the build. I incorporated Fedora 14 note and addition of the BB_NUMBER_THREADS and PARALLEL_MAKE variables. Signed-off-by: Scott Rifenbark --- .../yocto-project-qs/figures/yocto-environment.png | Bin 52531 -> 63851 bytes .../yocto-project-qs/yocto-project-qs.xml | 82 +++++++++++---------- 2 files changed, 45 insertions(+), 37 deletions(-) (limited to 'documentation/yocto-project-qs') diff --git a/documentation/yocto-project-qs/figures/yocto-environment.png b/documentation/yocto-project-qs/figures/yocto-environment.png index 10f34ac..04e6092 100755 Binary files a/documentation/yocto-project-qs/figures/yocto-environment.png and b/documentation/yocto-project-qs/figures/yocto-environment.png differ diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index 391336d..afffc02 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml @@ -48,7 +48,8 @@ - + The Yocto Project Development Environment @@ -199,8 +200,10 @@ The build creates an entire Linux system including the Toolchain from the source. - NOTE: The build process using Sato currently consumes 50GB of disk space. - To allow for variations in the build process and for future package expansion we recommend 100GB of free disk space. + NOTE: The build process using Sato currently consumes + 50GB of disk space. + To allow for variations in the build process and for future package expansion we + recommend 100GB of free disk space. @@ -208,44 +211,49 @@ $ wget http://www.yoctoproject.org/downloads/poky/poky-laverne-4.0.tar.bz2 $ tar xjf poky-laverne-4.0.tar.bz2 $ source poky-4.0/poky-init-build-env poky-4.0-build - $ cd poky-4.0-build - $ bitbake poky-image-sato - $ poky-qemu qemux86 - - - Here is some explanation for these commands: - - - - - The first two commands extract the Yocto Project files from the release area and place them into your build area (poky-4.0-build in this example). - - - - - The next two commands create the directory and place you there. - The build directory contains all the object files used during the build. - The default build directory is poky-dir/build. - Note that you can change the target architecture by editing the - <build_directory>/conf/local.conf file. - By default the target architecture is qemux86. - - - - - The $bitbake command builds the OS image for the target. - Here poky-image-sato is the name of the target. - - - - - Finally, the $poky-qemu command launches the customized QEMU. - - + The first two commands extract the Yocto Project files from the + release area and place them into a subdirectory of your current directory + (poky-4.0-build in this example). + The $ source command creates the directory and places + you there. + The build directory contains all the object files used during the build. + The default build directory is poky-4.0-build. + Note that you can change the target architecture by editing the + <build_directory>/conf/local.conf file. + By default the target architecture is qemux86. + + Now might be a good time to edit the conf/local.conf + file. + The defaults should all be fine. However, you might want to look at the variables + BB_NUMBER_THREADS and PARALLEL_MAKE. + By default, these variables are commented out. + + + Continue with the following command to build the OS image for the target, which is + poky-image-sato in this example. + + $ bitbake poky-image-sato + + NOTE: If you are running Fedora 14 or another distribution + with GNU make 3.82 you might have to run the following two + $bitbake commands instead: + + $ bitbake make-native + $ bitbake poky-image-sato + + The final command runs the image: + + $ poky-qemu qemux86 + + The build process could take several hours the first time you run it. + Depending on the number of processor and cores, the amount or RAM, the speed of your + internet connection and other factors. + After the initial build, subsequent builds run much faster. +
-- cgit v1.1