From 4741bb0c1c382ed0982ed82f420f2a3debf27487 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 13 Mar 2014 15:26:41 -0600 Subject: yocto-project-qs, poky.ent: Misc fixes in the Quick Start: I did the following to the yocto-project-qs.xml file: * I integrated some cross-referencing to the BitBake User Manual in a few spots. * I fixed a few grammar items. * I also noted the super user system uses four cores. I did the following to poky.ent: * Added a new variable for links into the BitBake User Manual. Variable is YOCTO_DOCS_BB_URL. (From yocto-docs rev: 3eba14c0dc9e71dfcf967d76e4525b26ac02c9c2) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/poky.ent | 1 + .../yocto-project-qs/yocto-project-qs.xml | 42 ++++++++++++++-------- 2 files changed, 28 insertions(+), 15 deletions(-) diff --git a/documentation/poky.ent b/documentation/poky.ent index 1ae0617d71..1cc9fab6b9 100644 --- a/documentation/poky.ent +++ b/documentation/poky.ent @@ -50,6 +50,7 @@ + diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index 77292d676b..e99a63726a 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml @@ -518,9 +518,11 @@ Continue with the following command to build an OS image for the target, which is core-image-sato in this example. For information on the -k option use the - bitbake --help command or see the - "BitBake" section in - the Yocto Project Reference Manual. + bitbake --help command, see the + "BitBake" + section in the Yocto Project Reference Manual, or see the + "BitBake Command" + section in the BitBake User Manual. $ bitbake -k core-image-sato @@ -534,12 +536,16 @@ $ runqemu qemux86 - - Depending on the number of processors and cores, the amount or RAM, the speed of your - Internet connection and other factors, the build process could take several hours the first - time you run it. - Subsequent builds run much faster since parts of the build are cached. - + + + Depending on the number of processors and cores, the amount + of RAM, the speed of your Internet connection and other + factors, the build process could take several hours the + first time you run it. + Subsequent builds run much faster since parts of the build + are cached. + + @@ -598,7 +604,7 @@ 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 - that represents the target architecture. + representing the target architecture. @@ -813,9 +819,10 @@ pages. - 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 12.04 system. + 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 12.04 system that + has four cores.
@@ -824,7 +831,7 @@ Set up your Source Directory - by using Git to clone the poky poky + by using Git to clone the poky repository and then check out the release branch: $ cd ~ @@ -860,7 +867,7 @@ At this point, the mybuilds directory has been created for you and it is now your current working directory. - If you don't provide your own directory name, + If you do not provide your own directory name, it defaults to build, which is inside the Source Directory. @@ -970,6 +977,11 @@ Once you have your image, you can take steps to load and boot it on the target hardware. + + + You can learn about BitBake in general by reading the + BitBake User Manual. +
-- cgit v1.2.3-54-g00ecf