diff --git a/bitbake/doc/user-manual/user-manual-execution.xml b/bitbake/doc/user-manual/user-manual-execution.xml index 148ac3e38a..d451ebb533 100644 --- a/bitbake/doc/user-manual/user-manual-execution.xml +++ b/bitbake/doc/user-manual/user-manual-execution.xml @@ -167,52 +167,53 @@ The following list shows common variables set: - BBDEBUG - - - MULTI_PROVIDER_WHITELIST + BB_NUMBER_THREADS BB_NUMBER_PARSE_THREADS - - BBPKGS - BB_DEFAULT_TASK + + BBMASK + + + BBPKGS + TOPDIR + + ASSUME_PROVIDED + + + PREFERRED_VERSION + + + PREFERRED_PROVIDERS + + + MULTI_PROVIDER_WHITELIST + + + BBFILE_COLLECTIONS + + + BBDEBUG + BB_VERBOSE_LOGS BB_NICE_LEVEL - - BBFILE_COLLECTIONS - - - ASSUME_PROVIDED - BB_DANGLINGAPPENDS_WARNONLY BBINCLUDED - - BBFILE_PRIORITY - - - BUILDNAME - - - BBMASK - - PREFERRED_VERSION - PREFERRED_PROVIDERS @@ -265,6 +266,10 @@ BitBake parses each recipe and append file located with BBFILES and stores the values of various variables into the datastore. + + Append files are applied in the order they are encountered in + BBFILES. + For each file, a fresh copy of the base configuration is made, then the recipe is parsed line by line. Any inherit statements cause BitBake to find and @@ -305,8 +310,8 @@ decisions about the recipe. Consequently, BitBake caches the values in which it is interested and does not store the rest of the information. - Experience has shown it's faster to re-parse the metadata than to - try and write it out to the disk and reload then it. + Experience has shown it is faster to re-parse the metadata than to + try and write it out to the disk and then reload it. @@ -426,10 +431,6 @@ versions until they have undergone sufficient testing to be considered stable. - - In summary, BitBake has created a list of providers, which is prioritized, for each target. - - When there are multiple “versions” of a given package, BitBake defaults to selecting the most recent @@ -464,6 +465,10 @@ PREFERRED_VERSION_a = "1.1" + + + In summary, BitBake has created a list of providers, which is prioritized, for each target. +
@@ -503,6 +508,12 @@ Based on the generated list of providers and the dependency information, BitBake can now calculate exactly what tasks it needs to run and in what order it needs to run them. + The + "Executing Tasks" section has more + information on how BitBake chooses which task to execute next. + + + The build now starts with BitBake forking off threads up to the limit set in the BB_NUMBER_THREADS variable.