summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-07-09 08:55:21 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-08-13 13:18:38 +0100
commit25146ba5dc249f3f5f19829eaee736a101615880 (patch)
treeb55baa73ad6015229d3b5f01d0f7c17b06406f3e
parent0345088d586da114890f764f85ed290b6bee0b64 (diff)
downloadpoky-25146ba5dc249f3f5f19829eaee736a101615880.tar.gz
ref-manual: Some additional edits
Made a pass through this before sending it out for review. (From yocto-docs rev: 702f65bb497b157dfd2635f9b13ffd679dda9d0a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/ref-manual/technical-details.xml35
1 files changed, 19 insertions, 16 deletions
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index 583d204566..79d16549c3 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -163,7 +163,7 @@
163 "<ulink url='&YOCTO_DOCS_QS_URL;#yp-intro'>Introducing the Yocto Project Development Environment</ulink>" 163 "<ulink url='&YOCTO_DOCS_QS_URL;#yp-intro'>Introducing the Yocto Project Development Environment</ulink>"
164 section of the Yocto Project Quick Start. 164 section of the Yocto Project Quick Start.
165 This expanded discussion presents a deeper level of detail regarding 165 This expanded discussion presents a deeper level of detail regarding
166 sources of input, generated output, and controlling 166 input, output, and
167 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>. 167 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>.
168 </para> 168 </para>
169 169
@@ -179,16 +179,16 @@
179 </para> 179 </para>
180 180
181 <para> 181 <para>
182 This paragraph will introduce the main blocks of the preceding figure 182 The generalized Yocto Project Devevelopment Environment consists of
183 to overview and organize the remainder of the section: 183 severl functional areas:
184 <itemizedlist> 184 <itemizedlist>
185 <listitem><para><emphasis>User Configuration:</emphasis> 185 <listitem><para><emphasis>User Configuration:</emphasis>
186 Methods by with the user can directly control the build 186 Metadata you can use to control the build process.
187 process.</para></listitem> 187 </para></listitem>
188 <listitem><para><emphasis>Metadata Layers:</emphasis> 188 <listitem><para><emphasis>Metadata Layers:</emphasis>
189 Various layers that provide software, machine, and 189 Various layers that provide software, machine, and
190 distro Metadata.</para></listitem> 190 distro Metadata.</para></listitem>
191 <listitem><para><emphasis>Soure Files:</emphasis> 191 <listitem><para><emphasis>Source Files:</emphasis>
192 Upstream releases, local projects, and SCMs.</para></listitem> 192 Upstream releases, local projects, and SCMs.</para></listitem>
193 <listitem><para><emphasis>Build System:</emphasis> 193 <listitem><para><emphasis>Build System:</emphasis>
194 Processes inside the BitBake "box". 194 Processes inside the BitBake "box".
@@ -196,14 +196,14 @@
196 patches, completes compilation, analyzes output for package 196 patches, completes compilation, analyzes output for package
197 generation, creates and tests packages, generates images, and 197 generation, creates and tests packages, generates images, and
198 generates cross-development tools.</para></listitem> 198 generates cross-development tools.</para></listitem>
199 <listitem><para><emphasis>Package Feeds</emphasis> 199 <listitem><para><emphasis>Package Feeds:</emphasis>
200 Package feeds into the BitBake process.</para></listitem> 200 Package feeds into the BitBake process.</para></listitem>
201 <listitem><para><emphasis>Images</emphasis> 201 <listitem><para><emphasis>Images:</emphasis>
202 Images produced by the development process. 202 Images produced by the development process.
203 Where do they go? 203 Where do they go?
204 Can you mess with them (i.e. freely delete them or move them?). 204 Can you mess with them (i.e. freely delete them or move them?).
205 </para></listitem> 205 </para></listitem>
206 <listitem><para><emphasis>Application Development SDK</emphasis> 206 <listitem><para><emphasis>Application Development SDK:</emphasis>
207 Cross-development tools that are produced along with an image 207 Cross-development tools that are produced along with an image
208 or separately with BitBake.</para></listitem> 208 or separately with BitBake.</para></listitem>
209 </itemizedlist> 209 </itemizedlist>
@@ -213,9 +213,13 @@
213 <title>User Configuration</title> 213 <title>User Configuration</title>
214 214
215 <para> 215 <para>
216 User configuration affects how you define the build. 216 User configuration helps define the build.
217 Through user configuration, you can tell BitBake the
218 target architecture for which you are building the image,
219 where to store downloaded source, and other build properties.
217 The following figure shows an expanded representation of the 220 The following figure shows an expanded representation of the
218 user configuration in the Yocto Project development environment: 221 user configuration box of the Yocto Project development
222 environment:
219 </para> 223 </para>
220 224
221 <mediaobject> 225 <mediaobject>
@@ -228,8 +232,8 @@
228 <para> 232 <para>
229 BitBake needs some basic configuration files in order to complete 233 BitBake needs some basic configuration files in order to complete
230 a build. 234 a build.
231 These files are <filename>*.conf</filename> files and the 235 These files are <filename>*.conf</filename> files.
232 minimally necessary ones reside as example files in the 236 The minimally necessary ones reside as example files in the
233 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. 237 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
234 For simplicity, this section refers to the Source Directory as 238 For simplicity, this section refers to the Source Directory as
235 the "Poky Directory." 239 the "Poky Directory."
@@ -328,8 +332,7 @@
328 <filename>auto.conf</filename> are not created by the environment 332 <filename>auto.conf</filename> are not created by the environment
329 initialization script. 333 initialization script.
330 If you want these configuration files, you must create them 334 If you want these configuration files, you must create them
331 yourself. 335 yourself:
332 Here a bit about what these files do:
333 <itemizedlist> 336 <itemizedlist>
334 <listitem><para><emphasis><filename>site.conf</filename>:</emphasis> 337 <listitem><para><emphasis><filename>site.conf</filename>:</emphasis>
335 I don't really know what this does. 338 I don't really know what this does.
@@ -348,7 +351,7 @@
348 </para> 351 </para>
349 352
350 <para> 353 <para>
351 All configuration files can undergo edits to further define 354 You can edit all configuration files to further define
352 the build. 355 the build.
353 This process is represented by the "User Configuration Edits" 356 This process is represented by the "User Configuration Edits"
354 box in the figure. 357 box in the figure.