diff options
Diffstat (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-providers.html')
| -rw-r--r-- | documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-providers.html | 63 |
1 files changed, 0 insertions, 63 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-providers.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-providers.html deleted file mode 100644 index 37d34a0e70..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-providers.html +++ /dev/null | |||
| @@ -1,63 +0,0 @@ | |||
| 1 | <html> | ||
| 2 | <head> | ||
| 3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
| 4 | <title>6.2. Preferences and Providers</title> | ||
| 5 | <link rel="stylesheet" type="text/css" href="../book.css"> | ||
| 6 | <meta name="generator" content="DocBook XSL Stylesheets V1.76.1"> | ||
| 7 | <link rel="home" href="index.html" title="The Yocto Project Reference Manual"> | ||
| 8 | <link rel="up" href="ref-bitbake.html" title="Chapter 6. BitBake"> | ||
| 9 | <link rel="prev" href="ref-bitbake-parsing.html" title="6.1. Parsing"> | ||
| 10 | <link rel="next" href="ref-bitbake-dependencies.html" title="6.3. Dependencies"> | ||
| 11 | </head> | ||
| 12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.2. Preferences and Providers"> | ||
| 13 | <div class="titlepage"><div><div><h2 class="title" style="clear: both"> | ||
| 14 | <a name="ref-bitbake-providers"></a>6.2. Preferences and Providers</h2></div></div></div> | ||
| 15 | <p> | ||
| 16 | Once all the <code class="filename">.bb</code> files have been | ||
| 17 | parsed, BitBake starts to build the target (<code class="filename">core-image-sato</code> | ||
| 18 | in the previous section's example) and looks for providers of that target. | ||
| 19 | Once a provider is selected, BitBake resolves all the dependencies for | ||
| 20 | the target. | ||
| 21 | In the case of <code class="filename">core-image-sato</code>, it would lead to | ||
| 22 | <code class="filename">packagegroup-core-x11-sato</code>, | ||
| 23 | which in turn leads to recipes like <code class="filename">matchbox-terminal</code>, | ||
| 24 | <code class="filename">pcmanfm</code> and <code class="filename">gthumb</code>. | ||
| 25 | These recipes in turn depend on <code class="filename">eglibc</code> and the toolchain. | ||
| 26 | </p> | ||
| 27 | <p> | ||
| 28 | Sometimes a target might have multiple providers. | ||
| 29 | A common example is "virtual/kernel", which is provided by each kernel package. | ||
| 30 | Each machine often selects the best kernel provider by using a line similar to the | ||
| 31 | following in the machine configuration file: | ||
| 32 | </p> | ||
| 33 | <pre class="literallayout"> | ||
| 34 | PREFERRED_PROVIDER_virtual/kernel = "linux-yocto" | ||
| 35 | </pre> | ||
| 36 | <p> | ||
| 37 | The default <code class="filename"><a class="link" href="ref-variables-glos.html#var-PREFERRED_PROVIDER" title="PREFERRED_PROVIDER">PREFERRED_PROVIDER</a></code> | ||
| 38 | is the provider with the same name as the target. | ||
| 39 | </p> | ||
| 40 | <p> | ||
| 41 | Understanding how providers are chosen is made complicated by the fact | ||
| 42 | that multiple versions might exist. | ||
| 43 | BitBake defaults to the highest version of a provider. | ||
| 44 | Version comparisons are made using the same method as Debian. | ||
| 45 | You can use the | ||
| 46 | <code class="filename"><a class="link" href="ref-variables-glos.html#var-PREFERRED_VERSION" title="PREFERRED_VERSION">PREFERRED_VERSION</a></code> | ||
| 47 | variable to specify a particular version (usually in the distro configuration). | ||
| 48 | You can influence the order by using the | ||
| 49 | <code class="filename"><a class="link" href="ref-variables-glos.html#var-DEFAULT_PREFERENCE" title="DEFAULT_PREFERENCE">DEFAULT_PREFERENCE</a></code> | ||
| 50 | variable. | ||
| 51 | By default, files have a preference of "0". | ||
| 52 | Setting the <code class="filename">DEFAULT_PREFERENCE</code> to "-1" makes the | ||
| 53 | package unlikely to be used unless it is explicitly referenced. | ||
| 54 | Setting the <code class="filename">DEFAULT_PREFERENCE</code> to "1" makes it likely the package is used. | ||
| 55 | <code class="filename">PREFERRED_VERSION</code> overrides any <code class="filename">DEFAULT_PREFERENCE</code> setting. | ||
| 56 | <code class="filename">DEFAULT_PREFERENCE</code> is often used to mark newer and more experimental package | ||
| 57 | versions until they have undergone sufficient testing to be considered stable. | ||
| 58 | </p> | ||
| 59 | <p> | ||
| 60 | In summary, BitBake has created a list of providers, which is prioritized, for each target. | ||
| 61 | </p> | ||
| 62 | </div></body> | ||
| 63 | </html> | ||