diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-03-13 15:26:41 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-03-25 12:29:38 +0000 |
commit | 4741bb0c1c382ed0982ed82f420f2a3debf27487 (patch) | |
tree | 3d3b38ecd59bc267a9fa4ed8130ff8b3f8ed448f /documentation/yocto-project-qs | |
parent | 35e026504e5ab757623c63d8e9a85343eb981868 (diff) | |
download | openembedded-core-contrib-4741bb0c1c382ed0982ed82f420f2a3debf27487.tar.gz |
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 <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/yocto-project-qs')
-rw-r--r-- | documentation/yocto-project-qs/yocto-project-qs.xml | 42 |
1 files changed, 27 insertions, 15 deletions
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 <filename>core-image-sato</filename> in this example. For information on the <filename>-k</filename> option use the - <filename>bitbake --help</filename> command or see the - "<ulink url='&YOCTO_DOCS_REF_URL;#usingpoky-components-bitbake'>BitBake</ulink>" section in - the Yocto Project Reference Manual. + <filename>bitbake --help</filename> command, see the + "<ulink url='&YOCTO_DOCS_REF_URL;#usingpoky-components-bitbake'>BitBake</ulink>" + section in the Yocto Project Reference Manual, or see the + "<ulink url='&YOCTO_DOCS_BB_URL;#user-manual-command'>BitBake Command</ulink>" + section in the BitBake User Manual. <literallayout class='monospaced'> $ bitbake -k core-image-sato </literallayout> @@ -534,12 +536,16 @@ <literallayout class='monospaced'> $ runqemu qemux86 </literallayout> - <note><para> - 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. - </para></note> + <note> + <para> + 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. + </para> + </note> </para> </section> @@ -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. </para> <literallayout class='monospaced'> @@ -813,9 +819,10 @@ pages. </para> </footnote> - 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. </para> <section id='getting-yocto'> @@ -824,7 +831,7 @@ <para> Set up your <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink> - by using Git to clone the <filename>poky</filename> poky + by using Git to clone the <filename>poky</filename> repository and then check out the release branch: <literallayout class='monospaced'> $ cd ~ @@ -860,7 +867,7 @@ </literallayout> 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, + If you do not provide your own directory name, it defaults to <filename>build</filename>, which is inside the Source Directory. </para> @@ -970,6 +977,11 @@ Once you have your image, you can take steps to load and boot it on the target hardware. </para> + + <para> + You can learn about BitBake in general by reading the + <ulink url='&YOCTO_DOCS_BB_URL;'>BitBake User Manual</ulink>. + </para> </section> </section> |