sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

documentation: dev-manual - minor edits and links added to glossary. 

(From yocto-docs rev: a5d66dd66458eab2ec4ca54f73ae0a46d44f430c)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2012-10-01 06:46:31 -07:00 committed by Richard Purdie
parent c63ff82422
commit 08996b37f4
1 changed files with 14 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -775,7 +775,7 @@
variable. variable.
BitBake passes these options into the <filename>make</filename> GNU invocation. BitBake passes these options into the <filename>make</filename> GNU invocation.
Note that a <filename>do_install</filename> task is still required. Note that a <filename>do_install</filename> task is still required.
Otherwise BitBake runs an empty <filename>do_install</filename> task by default. Otherwise, BitBake runs an empty <filename>do_install</filename> task by default.
</para> </para>
<para> <para>
@ -908,7 +908,9 @@
</para> </para>
<para> <para>
The <filename>PACKAGES</filename> and <filename>FILES_*</filename> variables in the The <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGES'><filename>PACKAGES</filename></ulink>
and <ulink url='&YOCTO_DOCS_REF_URL;#var-FILES'><filename>FILES_*</filename></ulink>
variables in the
<filename>meta/conf/bitbake.conf</filename> configuration file define how files installed <filename>meta/conf/bitbake.conf</filename> configuration file define how files installed
by the <filename>do_install</filename> task are packaged. by the <filename>do_install</filename> task are packaged.
By default, the <filename>PACKAGES</filename> variable contains By default, the <filename>PACKAGES</filename> variable contains
@ -1200,7 +1202,9 @@
Many standard recipes are already extended and support multiple libraries. Many standard recipes are already extended and support multiple libraries.
You can check in the <filename>meta/conf/multilib.conf</filename> You can check in the <filename>meta/conf/multilib.conf</filename>
configuration file in the source directory to see how this is configuration file in the source directory to see how this is
done using the <filename>BBCLASSEXTEND</filename> variable. done using the
<ulink url='&YOCTO_DOCS_REF_URL;#var-BBCLASSEXTEND'><filename>BBCLASSEXTEND</filename></ulink>
variable.
Eventually, all recipes will be covered and this list will be unneeded. Eventually, all recipes will be covered and this list will be unneeded.
</para> </para>
@ -1209,10 +1213,13 @@
extend the package name from <filename>${PN}</filename> to extend the package name from <filename>${PN}</filename> to
<filename>${MLPREFIX}${PN}</filename>, where <filename>MLPREFIX</filename> <filename>${MLPREFIX}${PN}</filename>, where <filename>MLPREFIX</filename>
is the particular multilib (e.g. "lib32-" or "lib64-"). is the particular multilib (e.g. "lib32-" or "lib64-").
Standard variables such as <filename>DEPENDS</filename>, Standard variables such as
<filename>RDEPENDS</filename>, <filename>RPROVIDES</filename>, <ulink url='&YOCTO_DOCS_REF_URL;#var-DEPENDS'><filename>DEPENDS</filename></ulink>,
<filename>RRECOMMENDS</filename>, <filename>PACKAGES</filename>, and <ulink url='&YOCTO_DOCS_REF_URL;#var-RDEPENDS'><filename>RDEPENDS</filename></ulink>,
<filename>PACKAGES_DYNAMIC</filename> are automatically extended by the system. <filename>RPROVIDES</filename>,
<ulink url='&YOCTO_DOCS_REF_URL;#var-RRECOMMENDS'><filename>RRECOMMENDS</filename></ulink>,
<ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGES'><filename>PACKAGES</filename></ulink>,
and <filename>PACKAGES_DYNAMIC</filename> are automatically extended by the system.
If you are extending any manual code in the recipe, you can use the If you are extending any manual code in the recipe, you can use the
<filename>${MLPREFIX}</filename> variable to ensure those names are extended <filename>${MLPREFIX}</filename> variable to ensure those names are extended
correctly. correctly.