diff options
| author |   Scott Rifenbark <srifenbark@gmail.com> | 2016-07-29 14:08:25 -0700 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-08-02 15:22:15 +0100 |
| commit | e205789361d6dd6945260f493c20072e4a716cf3 (patch) | |
| tree | 61bfc8451be73c519a8297e9049a7ac0e6110c7c /bitbake/doc | |
| parent | f0e73a4b65b8632bf9c9642faf8e1b22a628d88e (diff) | |
| download | openembedded-core-contrib-e205789361d6dd6945260f493c20072e4a716cf3.tar.gz | |
bitbake: bitbake-user-manual: Updated the PROVIDES variable
Fixes [YOCTO #10011]
Added paragraphs near the end to describe the role of virtual
targets.
(Bitbake rev: fc47bb99dbc1972dfb3a83c0f4c479963da64bcc)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/doc')
| -rw-r--r-- | bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml index a152218e32..dcf3ab3dd0 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml @@ -1976,6 +1976,27 @@ The <filename>PROVIDES</filename> statement results in the "libav" recipe also being known as "libpostproc". </para> + + <para> + In addition to providing recipes under alternate names, + the <filename>PROVIDES</filename> mechanism is also used + to implement virtual targets. + A virtual target is a name that corresponds to some + particular functionality (e.g. a Linux kernel). + Recipes that provide the functionality in question list the + virtual target in <filename>PROVIDES</filename>. + Recipes that depend on the functionality in question can + include the virtual target in + <link linkend='var-DEPENDS'><filename>DEPENDS</filename></link> + to leave the choice of provider open. + </para> + + <para> + Conventionally, virtual targets have names on the form + "virtual/function" (e.g. "virtual/kernel"). + The slash is simply part of the name and has no + syntactical significance. + </para> </glossdef> </glossentry> |