diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-04-22 14:23:29 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-05-22 17:23:38 +0100 |
| commit | 514176c231f71886a1a4be48a7a7a4fb43433e74 (patch) | |
| tree | e86088707d790323f89377b7a6e105c62c8c8208 /documentation/ref-manual | |
| parent | 818ec77cd3d0293ec5ef659e18a7e22d49f81737 (diff) | |
| download | poky-514176c231f71886a1a4be48a7a7a4fb43433e74.tar.gz | |
dev-manual, ref-manual: Minor edits suggested by Bill Traynor
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>
Diffstat (limited to 'documentation/ref-manual')
| -rw-r--r-- | documentation/ref-manual/ref-bitbake.xml | 5 | ||||
| -rw-r--r-- | documentation/ref-manual/usingpoky.xml | 4 |
2 files changed, 5 insertions, 4 deletions
diff --git a/documentation/ref-manual/ref-bitbake.xml b/documentation/ref-manual/ref-bitbake.xml index cc4c943506..717c58bd71 100644 --- a/documentation/ref-manual/ref-bitbake.xml +++ b/documentation/ref-manual/ref-bitbake.xml | |||
| @@ -23,8 +23,9 @@ | |||
| 23 | <note> | 23 | <note> |
| 24 | BitBake strives to be a generic "task" executor that is capable of handling complex dependency relationships. | 24 | BitBake strives to be a generic "task" executor that is capable of handling complex dependency relationships. |
| 25 | As such, it has no real knowledge of what the tasks being executed actually do. | 25 | As such, it has no real knowledge of what the tasks being executed actually do. |
| 26 | BitBake just considers a list of tasks with dependencies and handles metadata | 26 | BitBake just considers a list of tasks with dependencies and handles |
| 27 | that consists of variables in a certain format that get passed to the tasks. | 27 | <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> |
| 28 | consisting of variables in a certain format that get passed to the tasks. | ||
| 28 | </note> | 29 | </note> |
| 29 | 30 | ||
| 30 | <section id='ref-bitbake-parsing'> | 31 | <section id='ref-bitbake-parsing'> |
diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml index d27d6f7a5e..9a98b4560a 100644 --- a/documentation/ref-manual/usingpoky.xml +++ b/documentation/ref-manual/usingpoky.xml | |||
| @@ -38,8 +38,8 @@ | |||
| 38 | The <filename>build_dir</filename> is optional and specifies the directory the | 38 | The <filename>build_dir</filename> is optional and specifies the directory the |
| 39 | OpenEmbedded build system uses for the build - | 39 | OpenEmbedded build system uses for the build - |
| 40 | the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. | 40 | the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. |
| 41 | If you do not specify a Build Directory, it defaults to <filename>build</filename> | 41 | If you do not specify a Build Directory, it defaults to a directory |
| 42 | in your current working directory. | 42 | named <filename>build</filename> in your current working directory. |
| 43 | A common practice is to use a different Build Directory for different targets. | 43 | A common practice is to use a different Build Directory for different targets. |
| 44 | For example, <filename>~/build/x86</filename> for a <filename>qemux86</filename> | 44 | For example, <filename>~/build/x86</filename> for a <filename>qemux86</filename> |
| 45 | target, and <filename>~/build/arm</filename> for a <filename>qemuarm</filename> target. | 45 | target, and <filename>~/build/arm</filename> for a <filename>qemuarm</filename> target. |