linux/poky.git/documentation, branch yocto-2.5

kernel-dev: Clean up of "bsp_name" placeholder.

2018-03-25T08:41:13+00:00

This string is now being presented as "bsp_root_name" in the YP manual set. A BSP name is essentially "meta-bsp_root_name". It was being presented in the manual set as "meta-bsp_name", which is not technically correct. (From yocto-docs rev: 9ad25836b2b3ca79aa3430be014871f50205cf9e) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

bsp-guide: Updated BSP terminolgy and BBLAYERS ordering

2018-03-25T08:41:13+00:00

Fixed the way we refer to a BSP name. It is really "meta-" rather than "meta-". The name is the whole string and not just the root name. Also added a tip on ordering the layers in the BBLAYERS variable in the bblayers.conf file. Order is important. (From yocto-docs rev: 9c56238295f5631c496377616ea98b860253e6f7) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

ref-manual: Added term "container layer"

2018-03-25T08:41:13+00:00

This is a layer that contains other layers (From yocto-docs rev: 0cd1881c18e8a63d5f2f078b03fe4e89fd9c75b5) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

dev-manual: Cleaned up layer naming terminology

2018-03-25T08:41:13+00:00

Reality dictates that the YP does not treat layer naming consistently. Layers are talked about as the "meta-whatever" layer and never the "whatever" layer. However, the tooling sometimes appends or uses just the "whatever" part of the layer name. A good example is the meta-yocto-bsp configuration file. All the variables in there use just the root name of a layer's name. In the manuals, I had been distinguishing the layer name as just the "whatever" part sans "meta-". I talked about the convention of using "meta-" in front of layer names, etc. Well, this is confusing in light of how everyone says a layer's name is "meta-whatever". So, I fixed all this up. (From yocto-docs rev: 79e52f6ccf4246fc69a460ce9d3a4a18720a9442) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation: Updated the section on creating a general script

2018-03-25T08:41:13+00:00

Split this section into two sections: one for creating the layer using bitbake-layers create-layer and one for adding the layer to bblayers.conf using bitbake-layers add-layer. Needed to update some references in the yocto-project-qs and kernel-dev manuals. (From yocto-docs rev: 741a29b0cbeaaeaa0ac9155036ace2623938aee3) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

dev-manual: Created tip for using server outside of build area

2018-03-25T08:41:12+00:00

Fixes [YOCTO #12419] In the section on runtime package management, I created a "Tip" box to tell the user about using a location for the package index information outside of the "deploy" area of the hosts build directory. (From yocto-docs rev: 2aee814d3d3ed4052fca332693d5416907ae640e) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

dev-manual: Updates to the section on creating a layer

2018-03-25T08:41:12+00:00

Provided some key links to help clarify content. (From yocto-docs rev: 8d27b9946dad89729d30497bcc4de26b9a5c87d9) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

dev-manual: Sanity edit through the layer creation section

2018-03-25T08:41:12+00:00

(From yocto-docs rev: 91cda82ca148c56c18f059eeaa656d3561aed26d) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

dev-manual: Completed rewrite of runtime package management

2018-03-25T08:41:12+00:00

Fixes [YOCTO #12419] This section was unclear and needed some work. I added text to help clear things up. (From yocto-docs rev: 54358a39a5710dbd0cbcfe8dafd2f641ec3863ef) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

ref-manual: Updated PACKAGES_FEED_ARCHS variable

2018-03-25T08:41:12+00:00

Added the fact that this variable is really optional. If you don't use it then you are setting up a package feed URI that will include all supported arcchitectures for the package. Using it means you are setting up specific URIs for specific architectures. Added a "Tip" note box to show how you can use the variable to whitelist architectures. (From yocto-docs rev: 009f3551aa61aaf6459fd24105a2e06511b59da3) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie