summaryrefslogtreecommitdiffstats
path: root/documentation/overview-manual/overview-manual-concepts.xml
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2018-04-25 08:44:32 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-05-24 17:16:28 +0100
commitfa88ecd681ec1266ec67283500bd6df58c6be9ce (patch)
treefe433d25f980a791fa0875628fbd2631e82eeb16 /documentation/overview-manual/overview-manual-concepts.xml
parent3ea2c72bcca5c30ec3203001af178c3fc2b51d19 (diff)
downloadpoky-fa88ecd681ec1266ec67283500bd6df58c6be9ce.tar.gz
overview-manual: Updates to "OpenEmbedded Build System Concepts"
I removed the less than pretty build process figure and swapped in the more aesthetically pleasing one. Also, am refering to the figure as the "general workflow figure". (From yocto-docs rev: 093f1337131bc658d6afd1b56fb3661a76751aad) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/overview-manual/overview-manual-concepts.xml')
-rw-r--r--documentation/overview-manual/overview-manual-concepts.xml29
1 files changed, 18 insertions, 11 deletions
diff --git a/documentation/overview-manual/overview-manual-concepts.xml b/documentation/overview-manual/overview-manual-concepts.xml
index 8f32dc62b1..e17a973c9f 100644
--- a/documentation/overview-manual/overview-manual-concepts.xml
+++ b/documentation/overview-manual/overview-manual-concepts.xml
@@ -244,29 +244,35 @@
244 244
245 <para> 245 <para>
246 This section takes a more detailed look inside the build 246 This section takes a more detailed look inside the build
247 process used by the OpenEmbedded build system. 247 process used by the
248 The following diagram represents the build at a high level. 248 <ulink url='&YOCTO_DOCS_REF_URL;#build-system-term'>OpenEmbedded build system</ulink>,
249 which is the build system specific to the Yocto Project.
250 At the heart of the build system is BitBake, the task executor.
251 </para>
252
253 <para>
254 The following diagram represents a build at a high level.
249 The remainder of this section expands on the fundamental input, 255 The remainder of this section expands on the fundamental input,
250 output, process, and 256 output, process, and metadata logical blocks that make up the
251 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink> 257 OpenEmbedded build system's workflow.
252 blocks that make up the build process.
253 </para> 258 </para>
254 259
255 <para id='general-yocto-environment-figure'> 260 <para id='general-yocto-environment-figure'>
256 <imagedata fileref="figures/yocto-environment-ref.png" align="center" width="8in" depth="4.25in" /> 261 <imagedata fileref="figures/YP-flow-diagram.png" format="PNG" align='center' width="8in"/>
257 </para> 262 </para>
258 263
259 <para> 264 <para>
260 In general, the build process consists of several functional areas: 265 In general, the build's workflow consists of several functional
266 areas:
261 <itemizedlist> 267 <itemizedlist>
262 <listitem><para> 268 <listitem><para>
263 <emphasis>User Configuration:</emphasis> 269 <emphasis>User Configuration:</emphasis>
264 Metadata you can use to control the build process. 270 metadata you can use to control the build process.
265 </para></listitem> 271 </para></listitem>
266 <listitem><para> 272 <listitem><para>
267 <emphasis>Metadata Layers:</emphasis> 273 <emphasis>Metadata Layers:</emphasis>
268 Various layers that provide software, machine, and 274 Various layers that provide software, machine, and
269 distro Metadata. 275 distro metadata.
270 </para></listitem> 276 </para></listitem>
271 <listitem><para> 277 <listitem><para>
272 <emphasis>Source Files:</emphasis> 278 <emphasis>Source Files:</emphasis>
@@ -285,7 +291,8 @@
285 <emphasis>Package Feeds:</emphasis> 291 <emphasis>Package Feeds:</emphasis>
286 Directories containing output packages (RPM, DEB or IPK), 292 Directories containing output packages (RPM, DEB or IPK),
287 which are subsequently used in the construction of an 293 which are subsequently used in the construction of an
288 image or SDK, produced by the build system. 294 image or Software Development Kit (SDK), produced by the
295 build system.
289 These feeds can also be copied and shared using a web 296 These feeds can also be copied and shared using a web
290 server or other means to facilitate extending or updating 297 server or other means to facilitate extending or updating
291 existing images on devices at runtime if runtime package 298 existing images on devices at runtime if runtime package
@@ -293,7 +300,7 @@
293 </para></listitem> 300 </para></listitem>
294 <listitem><para> 301 <listitem><para>
295 <emphasis>Images:</emphasis> 302 <emphasis>Images:</emphasis>
296 Images produced by the development process. 303 Images produced by the workflow.
297 </para></listitem> 304 </para></listitem>
298 <listitem><para> 305 <listitem><para>
299 <emphasis>Application Development SDK:</emphasis> 306 <emphasis>Application Development SDK:</emphasis>