diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml index 84fb541598..e9f4cb022a 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 Getting Setup earlier in this manual + for information on how to get the BSP files. - + - 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 - meta-<BSP_name>. - The following command extracts the Crown Bay BSP into the current directory and names it - meta-crownbay: - - $ tar xjf crownbay-noemgd-1.1.tar.bz2 - - - - - If you cloned a poky Git repository - then you need to set up a different local Git repository - (meta-intel) for the BSP. + This example assumes a local meta-intel Git repository + inside the local poky Git repository. The meta-intel Git repository contains all the metadata that supports BSP creation. - When you set up the meta-intel Git repository you can - set it up anywhere you want. - We will set up the repository inside the - poky Git repository in this example. - The following transcript shows the steps to clone the meta-intel - Git repository inside the poky Git repository created earlier in this - example. - - $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. - - - - - Because meta-intel is its own Git repository you will want + 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 1.1 branch.