mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-09-16 00:49:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

dev-manual, ref-manual: Minor edits suggested by Bill Traynor

Browse Source 
Applied some re-wordings as suggested by Bill Traynor.

Reported-by: William M.A. Traynor <wmat@alphatroop.com>
(From yocto-docs rev: 2510d9795720afc0309a10b18605e5af4a83769b)

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
2013-04-22 14:23:29 -07:00
committed by Richard Purdie
parent 818ec77cd3
commit 514176c231
4 changed files with 14 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
documentation/ref-manual/ref-bitbake.xml
View File

@@ -23,8 +23,9 @@
<note>
BitBake strives to be a generic "task" executor that is capable of handling complex dependency relationships.
As such, it has no real knowledge of what the tasks being executed actually do.
BitBake just considers a list of tasks with dependencies and handles metadata
that consists of variables in a certain format that get passed to the tasks.
BitBake just considers a list of tasks with dependencies and handles
<ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>
consisting of variables in a certain format that get passed to the tasks.
</note>
<section id='ref-bitbake-parsing'>

4
documentation/ref-manual/usingpoky.xml
View File

@@ -38,8 +38,8 @@
The <filename>build_dir</filename> is optional and specifies the directory the
OpenEmbedded build system uses for the build -
the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
If you do not specify a Build Directory, it defaults to <filename>build</filename>
in your current working directory.
If you do not specify a Build Directory, it defaults to a directory
named <filename>build</filename> in your current working directory.
A common practice is to use a different Build Directory for different targets.
For example, <filename>~/build/x86</filename> for a <filename>qemux86</filename>
target, and <filename>~/build/arm</filename> for a <filename>qemuarm</filename> target.