From 6f488928cb25960e42794c20ce77f2b2978e4fa2 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 20 Feb 2018 15:25:49 -0800 Subject: ref-manual: Updated some terms in the "Terms" chapter. (From yocto-docs rev: c00be16a858ece1d3b02d554ec202088f78a2d1d) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-terms.xml | 136 +++++++++++++++++++++++---------- 1 file changed, 97 insertions(+), 39 deletions(-) (limited to 'documentation/ref-manual/ref-terms.xml') diff --git a/documentation/ref-manual/ref-terms.xml b/documentation/ref-manual/ref-terms.xml index 63fbf9c7b2..e746b4b7c6 100644 --- a/documentation/ref-manual/ref-terms.xml +++ b/documentation/ref-manual/ref-terms.xml @@ -135,8 +135,15 @@ Configuration File: - Configuration information in various .conf - files provides global definitions of variables. + Files that hold global definitions of variables, + user-defined variables, and hardware configuration + information. + These files tell the OpenEmbedded build system what to + build and what to put into the image to support a + particular platform. + + Configuration files end with a .conf + filename extension. The conf/local.conf configuration file in the Build Directory @@ -152,8 +159,6 @@ machine/beaglebone.conf configuration file defines variables for the Texas Instruments ARM Cortex-A8 development board). - Configuration files end with a .conf - filename extension. Cross-Development Toolchain: @@ -188,6 +193,17 @@ Yocto Project Application Development and the Extensible Software Development Kit (eSDK) manual. + + Extensible Software Development Kit (eSDK): + A custom SDK for application developers. + This eSDK allows developers to incorporate their library + and programming changes back into the image to make + their code available to other application developers. + + For information on the eSDK, see the + Yocto Project Application Development and Extensible Software Development Kit (eSDK) + manual. + Image: An image is an artifact of the BitBake build process given @@ -201,8 +217,25 @@ Layer: - A collection of recipes representing the core, - a BSP, or an application stack. + A collection of related recipes. + Layers allow you to consolidate related metadata to + customize your build. + Layers also isolate information used when building + for multiple architectures. + Layers are hierarchical in their ability to override + previous specifications. + You can include any number of available layers from the + Yocto Project and customize the build by adding your + layers after them. + You can search the Layer Index for layers used within + Yocto Project. + + For introductory information on layers, see the + "The Yocto Project Layer Model" + section in the Getting Started With Yocto Project Manual. + For more detailed information on layers, see the + "Understanding and Creating Layers" + section in the Yocto Project Development Tasks Manual. For a discussion specifically on BSP Layers, see the "BSP Layers" section in the Yocto Project Board Support Packages (BSP) @@ -210,22 +243,47 @@ Metadata: - The files that BitBake parses when building an image. - In general, Metadata includes recipes, classes, and - configuration files. - In the context of the kernel ("kernel Metadata"), the + A key element of the Yocto Project is the Metadata that + is used to construct a Linux distribution and is contained + in the files that the + OpenEmbedded build system + parses when building an image. + In general, Metadata includes recipes, configuration + files, and other information that refers to the build + instructions themselves, as well as the data used to + control what things get built and the effects of the + build. + Metadata also includes commands and data used to + indicate what versions of software are used, from + where they are obtained, and changes or additions to the + software itself (patches or auxiliary files) that + are used to fix bugs or customize the software for use + in a particular situation. + OpenEmbedded Core is an important set of validated + metadata. + + In the context of the kernel ("kernel Metadata"), the term refers to the kernel config fragments and features contained in the yocto-kernel-cache Git repository. - OE-Core: - A core set of Metadata originating with OpenEmbedded (OE) - that is shared between OE and the Yocto Project. - This Metadata is found in the meta - directory of the - Source Directory. + OpenEmbedded Core (OE-Core): + OE-Core is metadata comprised of foundational recipes, + classes, and associated files that are meant to be + common among many different OpenEmbedded-derived systems, + including the Yocto Project. + OE-Core is a curated subset of an original repository + developed by the OpenEmbedded community that has been + pared down into a smaller, core set of continuously + validated recipes. + The result is a tightly controlled and an quality-assured + core set of recipes. + + You can see the Metadata in the + meta directory of the Yocto Project + Source Repositories. OpenEmbedded Build System: @@ -285,37 +343,37 @@ Poky: - The term "poky", which is pronounced - Pock-ee, can mean several things: + Poky, which is pronounced Pock-ee, + is a reference embedded distribution and a reference + test configuration. + Poky provides the following: - In its most general sense, poky is an open-source - project that was initially developed by OpenedHand. - OpenedHand developed poky off of the existing - OpenEmbedded build system to create a commercially - supportable build system for embedded Linux. - After Intel Corporation acquired OpenedHand, the - poky project became the basis for the Yocto Project's - build system. + A base-level functional distro used to illustrate + how to customize a distribution. - Within the Yocto Project - Source Repositories, - "poky" exists as a separate Git - repository from which you can clone to yield a local - Git repository that is a copy on your host system. - Thus, "poky" can refer to the upstream or - local copy of the files used for development within - the Yocto Project. + A means by which to test the Yocto Project + components (i.e. Poky is used to validate + the Yocto Project). - Finally, "poky" can refer to the default - DISTRO - (i.e. distribution) created when you use the Yocto - Project in conjunction with the - poky repository to build an image. + A vehicle through which you can download + the Yocto Project. + Poky is not a product level distro. + Rather, it is a good starting point for customization. + + Poky began an open-source + project initially developed by OpenedHand. + OpenedHand developed Poky from the existing + OpenEmbedded build system to create a commercially + supportable build system for embedded Linux. + After Intel Corporation acquired OpenedHand, the + poky project became the basis for the Yocto Project's + build system. + Recipe: -- cgit v1.2.3-54-g00ecf