diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-10-22 14:16:22 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-10-23 00:03:17 +0100 |
commit | f735e50c63ac9f0cd15ad6ad38e46565846fffe8 (patch) | |
tree | e0e1db1324d48a9ab274a1b0ffff0be38affed4d /documentation/poky-ref-manual/usingpoky.xml | |
parent | be3c73bc02da6f1bb2698a5d8ddee1c4fdd0ba58 (diff) | |
download | poky-f735e50c63ac9f0cd15ad6ad38e46565846fffe8.tar.gz |
documentation: poky-ref-manual - Final changes before the 1.3 lockdown.
various changes as required.
(From yocto-docs rev: 7f166508337c9d4aadad23997470a8871c5e42a4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/poky-ref-manual/usingpoky.xml')
-rw-r--r-- | documentation/poky-ref-manual/usingpoky.xml | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml index 18bd8b7eb0..4ae6545479 100644 --- a/documentation/poky-ref-manual/usingpoky.xml +++ b/documentation/poky-ref-manual/usingpoky.xml | |||
@@ -30,20 +30,20 @@ | |||
30 | The first thing you need to do is set up the OpenEmbedded build environment by sourcing | 30 | The first thing you need to do is set up the OpenEmbedded build environment by sourcing |
31 | the environment setup script as follows: | 31 | the environment setup script as follows: |
32 | <literallayout class='monospaced'> | 32 | <literallayout class='monospaced'> |
33 | $ source oe-init-build-env [build_dir] | 33 | $ source &OE_INIT_FILE; [build_dir] |
34 | </literallayout> | 34 | </literallayout> |
35 | </para> | 35 | </para> |
36 | 36 | ||
37 | <para> | 37 | <para> |
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 <filename>build</filename> |
42 | in your current working directory. | 42 | 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. |
46 | See <link linkend="structure-core-script">oe-init-build-env</link> | 46 | See <link linkend="structure-core-script">&OE_INIT_FILE;</link> |
47 | for more information on this script. | 47 | for more information on this script. |
48 | </para> | 48 | </para> |
49 | 49 | ||
@@ -58,7 +58,7 @@ | |||
58 | The <filename>target</filename> is the name of the recipe you want to build. | 58 | The <filename>target</filename> is the name of the recipe you want to build. |
59 | Common targets are the images in <filename>meta/recipes-core/images</filename>, | 59 | Common targets are the images in <filename>meta/recipes-core/images</filename>, |
60 | <filename>/meta/recipes-sato/images</filename>, etc. all found in the | 60 | <filename>/meta/recipes-sato/images</filename>, etc. all found in the |
61 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. | 61 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. |
62 | Or, the target can be the name of a recipe for a specific piece of software such as | 62 | Or, the target can be the name of a recipe for a specific piece of software such as |
63 | <application>busybox</application>. | 63 | <application>busybox</application>. |
64 | For more details about the images the OpenEmbedded build system supports, see the | 64 | For more details about the images the OpenEmbedded build system supports, see the |
@@ -91,7 +91,7 @@ | |||
91 | <para> | 91 | <para> |
92 | Once an image has been built, it often needs to be installed. | 92 | Once an image has been built, it often needs to be installed. |
93 | The images and kernels built by the OpenEmbedded build system are placed in the | 93 | The images and kernels built by the OpenEmbedded build system are placed in the |
94 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink> in | 94 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> in |
95 | <filename class="directory">tmp/deploy/images</filename>. | 95 | <filename class="directory">tmp/deploy/images</filename>. |
96 | For information on how to run pre-built images such as <filename>qemux86</filename> | 96 | For information on how to run pre-built images such as <filename>qemux86</filename> |
97 | and <filename>qemuarm</filename>, see the | 97 | and <filename>qemuarm</filename>, see the |
@@ -268,7 +268,7 @@ | |||
268 | For guidance on how logging is handled in both Python and Bash recipes, see the | 268 | For guidance on how logging is handled in both Python and Bash recipes, see the |
269 | <filename>logging.bbclass</filename> file in the | 269 | <filename>logging.bbclass</filename> file in the |
270 | <filename>meta/classes</filename> folder of the | 270 | <filename>meta/classes</filename> folder of the |
271 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. | 271 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. |
272 | </para> | 272 | </para> |
273 | 273 | ||
274 | <section id='logging-with-python'> | 274 | <section id='logging-with-python'> |