From aa3a201629c7e40341f53d4be57b6e4223a845c8 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 9 Mar 2012 13:40:39 -0600 Subject: documentation/dev-manual: Converted to use poky.ent I converted the hard links to use the variables as established in the file poky.ent. Also, Cleaned up some bad text in the term "Yocto Project Files." Looks like a cut-and-paste problem. (From yocto-docs rev: e2e20bf4895d80dae73595e93132f37fb31121d1) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-bsp-appendix.xml | 43 +++++++++++----------- 1 file changed, 22 insertions(+), 21 deletions(-) (limited to 'documentation/dev-manual/dev-manual-bsp-appendix.xml') diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml index f9c4383567..035549431f 100644 --- a/documentation/dev-manual/dev-manual-bsp-appendix.xml +++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml @@ -1,5 +1,6 @@ +"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" +[ %poky; ] > @@ -45,10 +46,10 @@ Alternatively, you can start with the downloaded Poky "edison" tarball. These commands unpack the tarball into a Yocto Project File directory structure. By default, the top-level directory of the file structure is named - poky-edison-6.0: + poky-&YOCTO_POKY;: - $ tar xfj poky-edison-6.0.tar.bz2 - $ cd poky-edison-6.0 + $ tar xfj &YOCTO_POKY_TARBALL; + $ cd &YOCTO_POKY; If you're using the tarball method, you can ignore all the following steps that ask you to carry out Git operations. @@ -85,24 +86,24 @@ $ git branch -a $ git tag -l - For this example, we are going to use the Yocto Project 1.1 Release, which is code - named "edison". + For this example, we are going to use the Yocto Project &DISTRO; Release, which is code + named "&DISTRO_NAME;". To make sure we have a local area (branch in Git terms) on our machine that - reflects the 1.1 release, we can use the following commands: + reflects the &DISTRO; release, we can use the following commands: $ cd ~/poky $ git fetch --tags - $ git checkout edison-6.0 -b edison - Switched to a new branch 'edison' + $ git checkout &DISTRO_NAME;-&POKYVERSION; -b &DISTRO_NAME; + Switched to a new branch '&DISTRO_NAME;' The git fetch --tags is somewhat redundant since you just set up the repository and should have all the tags. The fetch command makes sure all the tags are available in your local repository. The Git checkout command with the -b option - creates a local branch for you named edison. - Your local branch begins in the same state as the Yocto Project 1.1 released tarball - marked with the edison-6.0 tag in the source repositories. + creates a local branch for you named &DISTRO_NAME;. + Your local branch begins in the same state as the Yocto Project &DISTRO; released tarball + marked with the &DISTRO_NAME;-&POKYVERSION; tag in the source repositories. @@ -160,14 +161,14 @@ Alternatively, you can start with the downloaded Crown Bay tarball. You can download the edison version of the BSP tarball from the - Download page of the + 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-edison-6.0.0.tar.bz2 + $ tar xfj crownbay-noemgd-&DISTRO_NAME;-6.0.0.tar.bz2 $ cd meta-intel @@ -181,10 +182,10 @@ skip to the next step. Because meta-intel is its own Git repository, you will want to be sure you are in the appropriate branch for your work. - For this example we are going to use the edison branch. + For this example we are going to use the &DISTRO_NAME; branch. - $ git checkout -b edison origin/edison - Switched to a new branch 'edison' + $ git checkout -b &DISTRO_NAME; origin/&DISTRO_NAME; + Switched to a new branch '&DISTRO_NAME;' @@ -271,7 +272,7 @@ meta-mymachine/conf/layer.conf. This file identifies build information needed for the new layer. You can see the - "Layer Configuration File" section + "Layer Configuration File" section in The Board Support Packages (BSP) Development Guide for more information on this configuration file. Basically, we are changing the existing statements to work with our BSP. @@ -483,7 +484,7 @@ the SRCREV statements. You can find all the machine and meta branch points (commits) for the linux-yocto-3.0 kernel at - . + . @@ -610,7 +611,7 @@ The appendix - + Reference: Variables Glossary in the Yocto Project Reference Manual has more information on configuration variables. -- cgit v1.2.3-54-g00ecf