From 2b93720cfcd7832d38ccf557cc54fc7565db1f24 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 18 Aug 2017 12:48:44 -0700 Subject: bsp-guide, dev-manual: Moved BSP Layer prep steps to bsp-guide The YP Development Manual had some build host preparation steps as part of the chapter that talks about getting a host ready for using YP. These steps are better suited in the BSP Guide. I moved them there and filled out the steps to be more complete. (From yocto-docs rev: 2277812d0dd411a103a4a4252d4cb90c471901c9) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/bsp-guide/bsp.xml | 153 +++++++++++++++++++++++++++++++++++++++- 1 file changed, 151 insertions(+), 2 deletions(-) (limited to 'documentation/bsp-guide/bsp.xml') diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index c6591cc284..6450c9d0aa 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -145,6 +145,155 @@ +
+ Preparing Your Build Host to Work With BSP Layers + + + This section describes how to get your build host ready + to work with BSP layers. + Once you have the host set up, you can create the layer + as described in the + "Creating a new BSP Layer Using the yocto-bsp Script" + section. + + For structural information on BSPs, see the + Example Filesystem Layout + section. + + + + Set Up the Build Environment: + Be sure you are set up to use BitBake in a shell. + See the + "Setting Up the Development Host to Use the Yocto Project" + section in the Yocto Project Development Manual for information + on how to get a build host ready that is either a native + Linux machine or a machine that uses CROPS. + + + Clone the poky Repository: + You need to have a local copy of the Yocto Project + Source Directory + (i.e. a local poky repository). + See the + "Cloning the poky Repository" + and possibly the + "Checking Out by Branch in Poky" + and + "Checking Out by Tag in Poky" + sections all in the Yocto Project Development Manual for + information on how to clone the poky + repository and check out the appropriate branch for your work. + + + Determine the BSP Layer You Want: + The Yocto Project supports many BSPs, which are maintained in + their own layers or in layers designed to contain several + BSPs. + To get an idea of machine support through BSP layers, you can + look at the + index of machines + for the release. + + + Optionally Clone the + meta-intel BSP Layer: + If your hardware is based on current Intel CPUs and devices, + you can leverage this BSP layer. + For details on the meta-intel BSP layer, + see the layer's + README + file. + + + Navigate to Your Source Directory: + Typically, you set up the + meta-intel Git repository + inside the + Source Directory + (e.g. poky). + + + Clone the Layer: + + $ git clone git://git.yoctoproject.org/meta-intel.git + Cloning into 'meta-intel'... + remote: Counting objects: 14224, done. + remote: Compressing objects: 100% (4591/4591), done. + remote: Total 14224 (delta 8245), reused 13985 (delta 8006) + Receiving objects: 100% (14224/14224), 4.29 MiB | 2.90 MiB/s, done. + Resolving deltas: 100% (8245/8245), done. + Checking connectivity... done. + + + + Check Out the Proper Branch: + The branch you check out for + meta-intel must match the same + branch you are using for the Yocto Project release + (e.g. &DISTRO_NAME_NO_CAP;): + + $ git checkout branch_name + + For an example on how to discover branch names and + checkout on a branch, see the + "Checking Out By Branch in Poky" + section. + + + + + Optionally Set Up an Alternative BSP Layer: + If your hardware can be more closely leveraged to an + existing BSP not within the meta-intel + BSP layer, you can clone that BSP layer. + + The process is identical to the process used for the + meta-intel layer except for the layer's + name. + For example, if you determine that your hardware most + closely matches the meta-minnow, + clone that layer: + + $ git clone git://git.yoctoproject.org/meta-minnow + Cloning into 'meta-minnow'... + remote: Counting objects: 456, done. + remote: Compressing objects: 100% (283/283), done. + remote: Total 456 (delta 163), reused 384 (delta 91) + Receiving objects: 100% (456/456), 96.74 KiB | 0 bytes/s, done. + Resolving deltas: 100% (163/163), done. + Checking connectivity... done. + + + + Initialize the Build Environment: + While in the root directory of the Source Directory (i.e. + poky), run the + &OE_INIT_FILE; + environment setup script to define the OpenEmbedded + build environment on your build host. + + $ source &OE_INIT_FILE; + + Among other things, the script creates the + Build Directory, + which is build in this case + and is located in the + Source Directory. + After the script runs, your current working directory + is set to the build directory. + + For information on running a memory-resident + BitBake, + see the + oe-init-build-env-memres + setup script. + + + + +
+
Example Filesystem Layout @@ -756,8 +905,8 @@ your system gives you access to layers you might be able to build on or modify to create your BSP. For information on how to get these files, see the - "Setting Up BSP Layers" - section in the Yocto Project Development Manual. + "Preparing Your Build Host to Work with BSP Layers" + section. Create Your Own BSP Layer Using the -- cgit v1.2.3-54-g00ecf