ref-manual: Tweaks to a patch from Robert P. J. Day
I altered three areas from the previous patch submitted and applied from Robert P. J. Day. Two minor wording changes and removal of negative language. (From yocto-docs rev: 0212b01f82637c3498f26bce57e98508c84799c5) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
c354dc6e4f
commit
437bf60876
|
@ -60,7 +60,8 @@
|
|||
and is responsible for parsing the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>,
|
||||
generating a list of tasks from it, and then executing those tasks.
|
||||
To see a list of the options BitBake supports, use either of:
|
||||
To see a list of the options BitBake supports, use either of
|
||||
the following commands:
|
||||
<literallayout class='monospaced'>
|
||||
$ bitbake -h
|
||||
$ bitbake --help
|
||||
|
@ -112,13 +113,13 @@
|
|||
The <filename>.bb</filename> files are usually referred to as "recipes."
|
||||
In general, a recipe contains information about a single piece of software.
|
||||
This information includes the location from which to download the
|
||||
pristine source, any source patches to be applied to that source
|
||||
(if any are needed), which special configuration options to apply,
|
||||
unaltered source, any source patches to be applied to that source
|
||||
(if needed), which special configuration options to apply,
|
||||
how to compile the source files, and how to package the compiled output.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The term "package" is sometimes (confusingly) used to refer to recipes. However,
|
||||
The term "package" is sometimes used to refer to recipes. However,
|
||||
since the word "package" is used for the packaged output from the OpenEmbedded
|
||||
build system (i.e. <filename>.ipk</filename> or <filename>.deb</filename> files),
|
||||
this document avoids using the term "package" when referring to recipes.
|
||||
|
|
Loading…
Reference in New Issue