diff options
| author | Richard Purdie <rpurdie@linux.intel.com> | 2010-09-10 12:32:48 +0100 |
|---|---|---|
| committer | Richard Purdie <rpurdie@linux.intel.com> | 2010-09-10 12:32:48 +0100 |
| commit | ad30f2cc4e1072ab5b2ec60de08f4d299118a255 (patch) | |
| tree | c50fab12544b530991a9993e7e23608d7c88214a /handbook/ref-structure.xml | |
| parent | 0a217cd18f09c837f67bf54956904a79fb013876 (diff) | |
| download | poky-ad30f2cc4e1072ab5b2ec60de08f4d299118a255.tar.gz | |
handbook: Various minor fixes
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Diffstat (limited to 'handbook/ref-structure.xml')
| -rw-r--r-- | handbook/ref-structure.xml | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/handbook/ref-structure.xml b/handbook/ref-structure.xml index 3d7c3c9db7..ca589de428 100644 --- a/handbook/ref-structure.xml +++ b/handbook/ref-structure.xml | |||
| @@ -40,10 +40,10 @@ | |||
| 40 | 40 | ||
| 41 | <para> | 41 | <para> |
| 42 | This directory contains user configuration files and the output | 42 | This directory contains user configuration files and the output |
| 43 | from Poky. It's now deprecated to be a sub-directory in Poky source tree, | 43 | generated by Poky in its standard configuration where the source tree is |
| 44 | though it's still supported. The desired way is to use <link | 44 | combined with the output. It is also possible to place output and configuration |
| 45 | linkend='structure-core-script'>seperate output directory</link> for build | 45 | files in a directory separate from the Poky source, see the section <link |
| 46 | outside of Poky source tree. | 46 | linkend='structure-core-script'>seperate output directory</link>. |
| 47 | </para> | 47 | </para> |
| 48 | </section> | 48 | </section> |
| 49 | 49 | ||
| @@ -136,7 +136,7 @@ | |||
| 136 | a shell makes changes to PATH and sets other core BitBake variables based on the | 136 | a shell makes changes to PATH and sets other core BitBake variables based on the |
| 137 | current working directory. You need to use this before running Poky commands. | 137 | current working directory. You need to use this before running Poky commands. |
| 138 | Internally it uses scripts within the <filename class="directory">scripts/ | 138 | Internally it uses scripts within the <filename class="directory">scripts/ |
| 139 | </filename> directory to do the bulk of the work. Now this script supports | 139 | </filename> directory to do the bulk of the work. This script supports |
| 140 | specifying any directory as the build output: | 140 | specifying any directory as the build output: |
| 141 | </para> | 141 | </para> |
| 142 | 142 | ||
| @@ -145,9 +145,9 @@ source POKY_SRC/poky-init-build-env [BUILDDIR] | |||
| 145 | </programlisting> | 145 | </programlisting> |
| 146 | 146 | ||
| 147 | <para> | 147 | <para> |
| 148 | Above command can be typed from any directory, as long as POKY_SRC points to | 148 | The above command can be typed from any directory, as long as POKY_SRC points to |
| 149 | the desired Poky source tree. The optional BUILDDIR could be any directory you'd | 149 | the desired Poky source tree. The optional BUILDDIR could be any directory you'd |
| 150 | like to contain output contents. | 150 | like Poky to generate the build output into. |
| 151 | </para> | 151 | </para> |
| 152 | </section> | 152 | </section> |
| 153 | </section> | 153 | </section> |
| @@ -182,7 +182,7 @@ source POKY_SRC/poky-init-build-env [BUILDDIR] | |||
| 182 | <para> | 182 | <para> |
| 183 | This file defines layers walked by bitbake. If there's no <filename> | 183 | This file defines layers walked by bitbake. If there's no <filename> |
| 184 | bblayers.conf</filename> present, it is created from <filename>bblayers.conf.sample | 184 | bblayers.conf</filename> present, it is created from <filename>bblayers.conf.sample |
| 185 | </filename>. | 185 | </filename> when the environment setup script is sourced. |
| 186 | </para> | 186 | </para> |
| 187 | </section> | 187 | </section> |
| 188 | 188 | ||
