diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2011-07-27 09:06:05 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-08-04 15:06:46 +0100 |
| commit | 0dbc9ba6119384a6fad8c0b33035b7e5bf483e07 (patch) | |
| tree | 5a04a9aeca04bea86252bf2f38fec7cc3c6a0c77 /documentation | |
| parent | 9709d1315d510f53e14f0bd19a875ebba3107b8f (diff) | |
| download | ast2050-yocto-poky-0dbc9ba6119384a6fad8c0b33035b7e5bf483e07.zip ast2050-yocto-poky-0dbc9ba6119384a6fad8c0b33035b7e5bf483e07.tar.gz | |
documentation/dev-manual/dev-manual-bsp-appendix.xml: re-wrote the Base BSP
I re-wrote the Getting your Base BSP section to reflect the example only.
Previously, there was a lot of information in there about getting BSP
files that was deemed universal and was moved to the getting started
chapter.
(From yocto-docs rev: addcbca37e3dfad27b388245a4085cd0a2747177)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/dev-manual/dev-manual-bsp-appendix.xml | 44 |
1 files changed, 6 insertions, 38 deletions
diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml index 84fb541..e9f4cb0 100644 --- a/documentation/dev-manual/dev-manual-bsp-appendix.xml +++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml @@ -90,51 +90,19 @@ download the BSP tarball and extract it, or set up a local Git repository that has the Yocto Project BSP layers. You should use the same method that you used to get the local Yocto Project files earlier. + See the <xref linkend='getting-setup'>Getting Setup</xref> earlier in this manual + for information on how to get the BSP files. </para> - - <para> - If you are using tarball extraction, simply download the tarball for the base - BSP you chose in the previous step and then extract it into any directory - you choose using the tar command. - Upon extraction, the BSP source directory (layer) will be named - <filename>meta-<BSP_name></filename>. - The following command extracts the Crown Bay BSP into the current directory and names it - <filename>meta-crownbay</filename>: - <literallayout class='monospaced'> - $ tar xjf crownbay-noemgd-1.1.tar.bz2 - </literallayout> - </para> - + <para> - If you cloned a <filename>poky</filename> Git repository - then you need to set up a different local Git repository - (<filename>meta-intel</filename>) for the BSP. + This example assumes a local <filename>meta-intel</filename> Git repository + inside the local <filename>poky</filename> Git repository. The <filename>meta-intel</filename> Git repository contains all the metadata that supports BSP creation. - When you set up the <filename>meta-intel</filename> Git repository you can - set it up anywhere you want. - We will set up the repository inside the - <filename>poky</filename> Git repository in this example. - </para> - - <para> - The following transcript shows the steps to clone the <filename>meta-intel</filename> - Git repository inside the <filename>poky</filename> Git repository created earlier in this - example. - <literallayout class='monospaced'> - $cd poky - $ git clone git://git.yoctoproject.org/meta-intel.git - Initialized empty Git repository in /home/scottrif/poky/meta-intel/.git/ - remote: Counting objects: 1325, done. - remote: Compressing objects: 100% (1078/1078), done. - remote: Total 1325 (delta 546), reused 85 (delta 27) - Receiving objects: 100% (1325/1325), 1.56 MiB | 330 KiB/s, done. - Resolving deltas: 100% (546/546), done. - </literallayout> </para> <para> - Because <filename>meta-intel</filename> is its own Git repository you will want + Because <filename>meta-intel</filename> 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 <filename>1.1</filename> branch. <literallayout class='monospaced'> |
