From c0433b3b9409610481d49f2563dbc57c8995dbf8 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 14 Jun 2012 14:41:22 -0700 Subject: documentation/dev-manual: Minor 1.1.2 updates The second pass through the manual testing against the variables put in during the first pass. Minor changes and few links not right. One thing of note is the tarball used for the BSP appendix example for Crown Bay. The tarball I have in there is the release 1.1 version with poky 6.0.0. (From yocto-docs rev: 3839c0b0a063fd240b129c745ee95047a6e23cb8) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-bsp-appendix.xml | 4 ++-- documentation/dev-manual/dev-manual-intro.xml | 7 +++++-- documentation/dev-manual/dev-manual-newbie.xml | 16 +++++++--------- 3 files changed, 14 insertions(+), 13 deletions(-) diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml index 74d5406f4b..4d4bc0102b 100644 --- a/documentation/dev-manual/dev-manual-bsp-appendix.xml +++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml @@ -161,11 +161,11 @@ Download page of the Yocto Project website. Here is the specific link for the tarball needed for this example: - . + . Again, be sure that you are already in the poky directory as described previously before installing the tarball: - $ tar xfj crownbay-noemgd-&DISTRO_NAME;-&POKYVERSION;.tar.bz2 + $ tar xfj crownbay-noemgd-&DISTRO_NAME;-6.0.0.tar.bz2 $ cd meta-intel diff --git a/documentation/dev-manual/dev-manual-intro.xml b/documentation/dev-manual/dev-manual-intro.xml index b9a63225ab..0728753358 100644 --- a/documentation/dev-manual/dev-manual-intro.xml +++ b/documentation/dev-manual/dev-manual-intro.xml @@ -18,7 +18,8 @@ sources where you can find more detail. For example, detailed information on Git, repositories and open source in general can be found in many places. - Another example is how to get set up to use the Yocto Project, which our Yocto Project Quick Start covers. + Another example is how to get set up to use the Yocto Project, which our + Yocto Project Quick Start covers. @@ -64,7 +65,9 @@ Step-by-step instructions if those instructions exist in other Yocto Project documentation. - For example, the Application Development Toolkit (ADT) User’s Guide contains detailed + For example, the + Yocto Project Application Development Toolkit (ADT) + User's Guide contains detailed instruction on how to obtain and configure the Eclipse Yocto Plug-in. Reference material. diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index bc95a20c2a..774ac3d5bf 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml @@ -171,10 +171,8 @@ Images are the binary output that runs on specific hardware and for specific use cases. For a list of the supported image types that the Yocto Project provides, see the - "Reference: Images" - appendix in - - The Yocto Project Reference Manual. + "Reference: Images" + appendix in the Yocto Project Reference Manual. Layer: A collection of recipes representing the core, a BSP, or an application stack. Metadata: The files that BitBake parses when building an image. @@ -217,14 +215,14 @@ system in order to do any development using the Yocto Project. The name of the top-level directory of the Yocto Project file structure is derived from the Yocto Project release tarball. - For example, downloading and unpacking poky-edison-6.0.1.tar.bz2 + For example, downloading and unpacking &YOCTO_POKY_TARBALL; results in a Yocto Project file structure whose Yocto Project source directory is named - poky-edison-6.0.1. + &YOCTO_POKY;. If you create a Git repository, then you can name the repository anything you like. You can find instruction on how to set up the Yocto Project files on your host development system by reading the - "Getting + "Getting Setup" section. Yocto Project Build Directory: This term refers to the area used by the Yocto Project for builds. @@ -234,9 +232,9 @@ You can create the Yocto Project build directory anywhere you want on your development system. Here is an example that creates the directory in mybuilds - and names the Yocto Project build directory YP-6.0.1: + and names the Yocto Project build directory YP-&POKYVERSION;: - $ source poky-edison-6.0.1/oe-init-build-env $HOME/mybuilds/YP-6.0.1 + $ source &OE_INIT_PATH; $HOME/mybuilds/YP-&POKYVERSION; If you don't specifically name the directory, BitBake creates it in the current directory and uses the name build. -- cgit v1.2.3-54-g00ecf