From 15353f7d81b50eea439847adf80441165a7c1d26 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 25 Apr 2018 11:45:44 -0700 Subject: overview-manual: Updates to "User Configuration" section. This section was pretty out of date. I have updated many areas of the text. (From yocto-docs rev: 640cdc7fb9d4f93c86b907d631e4f90b261d5ea1) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../overview-manual/overview-manual-concepts.xml | 84 +++++++++++++--------- 1 file changed, 51 insertions(+), 33 deletions(-) (limited to 'documentation/overview-manual/overview-manual-concepts.xml') diff --git a/documentation/overview-manual/overview-manual-concepts.xml b/documentation/overview-manual/overview-manual-concepts.xml index e17a973c9f..b8d1fa2b92 100644 --- a/documentation/overview-manual/overview-manual-concepts.xml +++ b/documentation/overview-manual/overview-manual-concepts.xml @@ -251,13 +251,14 @@ - The following diagram represents a build at a high level. + The following diagram represents the high-level workflow of a + build. The remainder of this section expands on the fundamental input, output, process, and metadata logical blocks that make up the - OpenEmbedded build system's workflow. + workflow. - + @@ -323,7 +324,7 @@ The following figure shows an expanded representation of the "User Configuration" box of the - general Build Process figure: + general workflow figure: @@ -335,21 +336,22 @@ complete a build. These files are *.conf files. The minimally necessary ones reside as example files in the + build/conf directory of the Source Directory. For simplicity, this section refers to the Source Directory as the "Poky Directory." - When you clone the poky Git repository - or you download and unpack a Yocto Project release, you - can set up the Source Directory to be named anything you want. + When you clone the + Poky + Git repository or you download and unpack a Yocto Project + release, you can set up the Source Directory to be named + anything you want. For this discussion, the cloned repository uses the default name poky. - The - Poky - repository is primarily an aggregation of existing + The Poky repository is primarily an aggregation of existing repositories. It is not a canonical upstream source. @@ -360,10 +362,9 @@ a conf directory that has example configuration files. These example files are used as a basis for creating actual - configuration files when you source the build environment - script - (i.e. - &OE_INIT_FILE;). + configuration files when you source + &OE_INIT_FILE;, + which is the build environment script. @@ -415,18 +416,9 @@ To see the default configurations in a local.conf file created by the build environment script, see the - local.conf.sample in the - meta-poky layer: + local.conf.sample + in the meta-poky layer: - - Parallelism Options: - Controlled by the - BB_NUMBER_THREADS, - PARALLEL_MAKE, - and - BB_NUMBER_PARSE_THREADS - variables. - Target Machine Selection: Controlled by the @@ -451,6 +443,30 @@ TMPDIR variable. + + Distribution Policy: + Controlled by the + DISTRO + variable. + + + Packaging Format: + Controlled by the + PACKAGE_CLASSES + variable. + + + SDK Target Architecture: + Controlled by the + SDKMACHINE + variable. + + + Extra Image Packages: + Controlled by the + EXTRA_IMAGE_FEATURES + variable. + Configurations set in the @@ -540,7 +556,9 @@ site.conf, auto.conf, and local.conf. And, the build system applies the normal assignment statement - rules. + rules as described in the + "Syntax and Operators" + chapter of the BitBake User Manual. Because the files are parsed in a specific order, variable assignments for the same variable could be affected. For example, if the auto.conf file and @@ -594,7 +612,7 @@ The following figure shows an expanded representation of the Metadata, Machine Configuration, and Policy Configuration input (layers) boxes of the - general Build Process figure: + general workflow figure: @@ -757,7 +775,7 @@ In order for the OpenEmbedded build system to create an image or any target, it must be able to access source files. The - general Build Process figure + general workflow figure represents source files using the "Upstream Project Releases", "Local Projects", and "SCMs (optional)" boxes. The figure represents mirrors, which also play a role in @@ -821,7 +839,7 @@ The remainder of this section provides a deeper look into the source files and the mirrors. Here is a more detailed look at the source file area of the - general Build Process figure: + general workflow figure: @@ -934,7 +952,7 @@ in the Build Directory. The - general Build Process figure + general workflow figure shows this package feeds area in the upper-right corner. @@ -1028,7 +1046,7 @@ BitBake to produce images. You can see from the - general Build Process figure, + general workflow figure, the BitBake area consists of several functional areas. This section takes a closer look at each of those areas. @@ -1785,7 +1803,7 @@ are compressed forms of the root filesystem that are ready to boot on a target device. You can see from the - general Build Process figure + general workflow figure that BitBake output, in part, consists of images. This section is going to look more closely at this output: @@ -1881,7 +1899,7 @@ In the - general Yocto Project Development Environment figure, + general Yocto Project Development Environment figure, the output labeled "Application Development SDK" represents an SDK. The SDK generation process differs depending on whether you -- cgit v1.2.3-54-g00ecf