ref-manual: Various small corrections to package-related stuff

Fixes [YOCTO #10135]

Some small problems were fixed:

 * Added a cross-reference in the FILES glossary entry to the
   PACKAGES variable.  The two are tied and there was not a
   reference to it.

 * Removed a redundant "/" character in a pathname example in
   the dev-manual.

 * Removed a redundant "/" character in an example pathname
   in the FILES glossary description.

(From yocto-docs rev: 11a397c232696deece7ac5c6dafcadb87d7a5775)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2016-08-12 14:10:02 -07:00 committed by Richard Purdie
parent f82a65776b
commit feda248d59
3 changed files with 9 additions and 5 deletions

View File

@ -3048,7 +3048,7 @@
PV = "1.5.1+git${SRCPV}"
S = "${WORKDIR}/git/"
S = "${WORKDIR}/git"
EXTRA_OEMAKE = "'CC=${CC}' 'RANLIB=${RANLIB}' 'AR=${AR}' 'CFLAGS=${CFLAGS} -I${S}/include -DWITHOUT_XATTR' 'BUILDDIR=${S}'"

View File

@ -4160,12 +4160,16 @@
<glossentry id='var-FILES'><glossterm>FILES</glossterm>
<info>
FILES[doc] = "The list of directories or files that are placed in packages."
FILES[doc] = "The list of directories or files that are placed in a package."
</info>
<glossdef>
<para role="glossdeffirst">
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
The list of directories or files that are placed in packages.
The list of files and directories that are placed in a
package.
The
<link linkend='var-PACKAGES'><filename>PACKAGES</filename></link>
variable lists the packages generated by a recipe.
</para>
<para>
@ -4176,7 +4180,7 @@
resulting package.
Here is an example:
<literallayout class='monospaced'>
FILES_${PN} += "${bindir}/mydir1/ ${bindir}/mydir2/myfile"
FILES_${PN} += "${bindir}/mydir1 ${bindir}/mydir2/myfile"
</literallayout>
</para>

View File

@ -338,7 +338,7 @@
<title>Running Specific Tasks</title>
<para>
Any given package consists of a set of tasks.
Any given recipe consists of a set of tasks.
The standard BitBake behavior in most cases is:
<filename>do_fetch</filename>,
<filename>do_unpack</filename>,