summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-06-14 18:46:49 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-06-29 13:59:25 (GMT)
commit9f915d46be73769c4b02f38fee14761b1b43958d (patch)
treeb77755c424bd36e6438c860cffd819ac6ae68138
parenta6f25334ec17091a8b4e1f4cd1f12217a1cd5950 (diff)
downloadpoky-9f915d46be73769c4b02f38fee14761b1b43958d.tar.gz
documentation/dev-manual/dev-manual-start.xml: 1.1.2 variables and updates
First pass at implementing the poky.ent variables. Also changes text where appropriate. (From yocto-docs rev: a9f31065ee0261d82fcac1f3db3ad98587418c15) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-start.xml156
1 files changed, 101 insertions, 55 deletions
diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
index d9f042b..d7a046b 100644
--- a/documentation/dev-manual/dev-manual-start.xml
+++ b/documentation/dev-manual/dev-manual-start.xml
@@ -1,5 +1,6 @@
1<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 1<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
2"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> 2"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
3[<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
3 4
4<chapter id='dev-manual-start'> 5<chapter id='dev-manual-start'>
5 6
@@ -9,7 +10,7 @@
9 This chapter introduces the Yocto Project and gives you an idea of what you need to get started. 10 This chapter introduces the Yocto Project and gives you an idea of what you need to get started.
10 You can find enough information to set up your development host and build or use images for 11 You can find enough information to set up your development host and build or use images for
11 hardware supported by the Yocto Project by reading 12 hardware supported by the Yocto Project by reading
12 <ulink url='http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html'> 13 <ulink url='&YOCTO_DOCS_QS_URL;'>
13 The Yocto Project Quick Start</ulink>. 14 The Yocto Project Quick Start</ulink>.
14</para> 15</para>
15 16
@@ -30,20 +31,21 @@
30 </para> 31 </para>
31 32
32 <para> 33 <para>
33 You can use the Yocto Project, which uses the BitBake build tool, to develop complete Linux 34 You can use the Yocto Project build system, which uses
35 <ulink url='http://bitbake.berlios.de/manual/'>BitBake</ulink>, to develop complete Linux
34 images and associated user-space applications for architectures based on ARM, MIPS, PowerPC, 36 images and associated user-space applications for architectures based on ARM, MIPS, PowerPC,
35 x86 and x86-64. 37 x86 and x86-64.
36 While the Yocto Project does not provide a strict testing framework, 38 While the Yocto Project does not provide a strict testing framework,
37 it does provide or generate for you artifacts that let you perform target-level and 39 it does provide or generate for you artifacts that let you perform target-level and
38 emulated testing and debugging. 40 emulated testing and debugging.
39 And, if you are an <trademark class='trade'>Eclipse</trademark> 41 Additionally, if you are an <trademark class='trade'>Eclipse</trademark>
40 IDE user, you can install an Eclipse Yocto Plug-in to allow you to 42 IDE user, you can install an Eclipse Yocto Plug-in to allow you to
41 develop within that familiar environment. 43 develop within that familiar environment.
42 </para> 44 </para>
43</section> 45</section>
44 46
45<section id='getting-setup'> 47<section id='getting-setup'>
46 <title>Getting Setup</title> 48 <title>Getting Set Up</title>
47 49
48 <para> 50 <para>
49 Here is what you need to get set up to use the Yocto Project: 51 Here is what you need to get set up to use the Yocto Project:
@@ -57,7 +59,7 @@
57 </para></listitem> 59 </para></listitem>
58 <listitem><para><emphasis>Packages:</emphasis> The Yocto Project requires certain packages 60 <listitem><para><emphasis>Packages:</emphasis> The Yocto Project requires certain packages
59 exist on your development system (e.g. Python 2.6 or 2.7). 61 exist on your development system (e.g. Python 2.6 or 2.7).
60 See "<ulink url='http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html#packages'>The Packages</ulink>" 62 See "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>"
61 section in the Yocto Project Quick start for the exact package 63 section in the Yocto Project Quick start for the exact package
62 requirements and the installation commands to install them 64 requirements and the installation commands to install them
63 for the supported distributions.</para></listitem> 65 for the supported distributions.</para></listitem>
@@ -73,29 +75,37 @@
73 <itemizedlist> 75 <itemizedlist>
74 <listitem><para><emphasis>Tarball Extraction:</emphasis> If you are not going to contribute 76 <listitem><para><emphasis>Tarball Extraction:</emphasis> If you are not going to contribute
75 back into the Yocto Project, you can simply download the Yocto Project release you want 77 back into the Yocto Project, you can simply download the Yocto Project release you want
76 from the website’s <ulink url='http://yoctoproject.org/download'>download page</ulink>. 78 from the website’s <ulink url='&YOCTO_HOME_URL;/download'>download page</ulink>.
77 Once you have the tarball, just extract it into a directory of your choice.</para> 79 Once you have the tarball, just extract it into a directory of your choice.</para>
78 <para>For example, the following command extracts the Yocto Project 1.1.1 release tarball 80 <para>For example, the following command extracts the Yocto Project &DISTRO;
81 release tarball
79 into the current working directory and sets up the Yocto Project file structure 82 into the current working directory and sets up the Yocto Project file structure
80 with a top-level directory named <filename>poky-edison-6.0.1</filename>: 83 with a top-level directory named <filename>&YOCTO_POKY;</filename>:
81 <literallayout class='monospaced'> 84 <literallayout class='monospaced'>
82 $ tar xfj poky-edison-6.0.1.tar.bz2 85 $ tar xfj &YOCTO_POKY_TARBALL;
83 </literallayout></para> 86 </literallayout></para>
84 <para>This method does not produce a Git repository. 87 <para>This method does not produce a Git repository.
85 Instead, you simply end up with a local snapshot of the 88 Instead, you simply end up with a local snapshot of the
86 Yocto Project files that are based on the particular release in the 89 Yocto Project files that are based on the particular release in the
87 tarball.</para></listitem> 90 tarball.</para></listitem>
88 <listitem><para><emphasis>Git Repository Method:</emphasis> If you are going to be contributing 91 <listitem><para><emphasis>Git Repository Method:</emphasis> If you are going to be contributing
89 back into the Yocto Project, you should use Git commands to set up a local 92 back into the Yocto Project or you simply want to keep up
90 Git repository of the Yocto Project files. 93 with the latest developments, you should use Git commands to set up a local
94 Git repository of the Yocto Project files.
91 Doing so creates a Git repository with a complete history of changes and allows 95 Doing so creates a Git repository with a complete history of changes and allows
92 you to easily submit your changes upstream to the project.</para> 96 you to easily submit your changes upstream to the project.
93 <para>The following transcript shows how to clone the Yocto Project files' 97 Because you cloned the repository, you have access to all the Yocto Project development
94 Git repository into the current working directory. 98 branches and tag names used in the upstream repository.</para>
95 The command creates the repository in a directory named <filename>poky</filename>. 99 <para>The following transcript shows how to clone the Yocto Project Files'
96 For information on the Yocto Project and Git, see the 100 Git repository into the current working directory.
97 "<link linkend='git'>Git</link>" section. 101 <note>The name of the Yocto Project Files Git repository in the Yocto Project Files
98 <literallayout class='monospaced'> 102 Source Repositories is <filename>poky</filename>.
103 You can view the Yocto Project Source Repositories at
104 <ulink url='&YOCTO_GIT_URL;/cgit.cgi'></ulink></note>
105 The command creates the local repository in a directory named <filename>poky</filename>.
106 For information on Git used within the Yocto Project, see the
107 "<link linkend='git'>Git</link>" section.
108 <literallayout class='monospaced'>
99 $ git clone git://git.yoctoproject.org/poky 109 $ git clone git://git.yoctoproject.org/poky
100 Initialized empty Git repository in /home/scottrif/poky/.git/ 110 Initialized empty Git repository in /home/scottrif/poky/.git/
101 remote: Counting objects: 116882, done. 111 remote: Counting objects: 116882, done.
@@ -104,15 +114,18 @@
104 Receiving objects: 100% (116882/116882), 72.13 MiB | 2.68 MiB/s, done. 114 Receiving objects: 100% (116882/116882), 72.13 MiB | 2.68 MiB/s, done.
105 Resolving deltas: 100% (80651/80651), done. </literallayout></para> 115 Resolving deltas: 100% (80651/80651), done. </literallayout></para>
106 <para>For another example of how to set up your own local Git repositories, see this 116 <para>For another example of how to set up your own local Git repositories, see this
107 <ulink url='https://wiki.yoctoproject.org/wiki/Transcript:_from_git_checkout_to_meta-intel_BSP'> 117 <ulink url='&YOCTO_WIKI_URL;/wiki/Transcript:_from_git_checkout_to_meta-intel_BSP'>
108 wiki page</ulink>, which describes how to create both <filename>poky</filename> 118 wiki page</ulink>, which describes how to create both <filename>poky</filename>
109 and <filename>meta-intel</filename> Git repositories.</para></listitem> 119 and <filename>meta-intel</filename> Git repositories.</para></listitem>
110 </itemizedlist></para></listitem> 120 </itemizedlist></para></listitem>
111 <listitem id='local-kernel-files'><para><emphasis>Linux Yocto Kernel:</emphasis> 121 <listitem id='local-kernel-files'><para><emphasis>Linux Yocto Kernel:</emphasis>
112 If you are going to be making modifications to a supported Linux Yocto kernel, you 122 If you are going to be making modifications to a supported Linux Yocto kernel, you
113 need to establish local copies of the source. 123 need to establish local copies of the source.
114 This setup involves creating a bare clone of the Linux Yocto kernel and then cloning 124 You can find Git repositories of supported Linux Yocto Kernels organized under
115 that repository. 125 "Yocto Linux Kernel" in the Yocto Project Source Repositories at
126 <ulink url='&YOCTO_GIT_URL;/cgit.cgi'></ulink>.</para>
127 <para>This setup involves creating a bare clone of the Linux Yocto kernel and then
128 copying that cloned repository.
116 You can create the bare clone and the copy of the bare clone anywhere you like. 129 You can create the bare clone and the copy of the bare clone anywhere you like.
117 For simplicity, it is recommended that you create these structures outside of the 130 For simplicity, it is recommended that you create these structures outside of the
118 Yocto Project files' Git repository.</para> 131 Yocto Project files' Git repository.</para>
@@ -122,8 +135,8 @@
122 <note>When you have a local Linux Yocto kernel Git repository, you can 135 <note>When you have a local Linux Yocto kernel Git repository, you can
123 reference that repository rather than the upstream Git repository as 136 reference that repository rather than the upstream Git repository as
124 part of the <filename>clone</filename> command. 137 part of the <filename>clone</filename> command.
125 Doing so can speed up the process.</note> 138 Doing so can speed up the process.</note></para>
126 In the following example, the bare clone is named 139 <para>In the following example, the bare clone is named
127 <filename>linux-yocto-3.0-1.1.x.git</filename>, while the 140 <filename>linux-yocto-3.0-1.1.x.git</filename>, while the
128 copy is named <filename>my-linux-yocto-3.0-1.1.x-work</filename>: 141 copy is named <filename>my-linux-yocto-3.0-1.1.x-work</filename>:
129 <literallayout class='monospaced'> 142 <literallayout class='monospaced'>
@@ -143,20 +156,23 @@
143 </literallayout></para></listitem> 156 </literallayout></para></listitem>
144 <listitem id='poky-extras-repo'><para><emphasis> 157 <listitem id='poky-extras-repo'><para><emphasis>
145 The <filename>poky-extras</filename> Git Repository</emphasis>: 158 The <filename>poky-extras</filename> Git Repository</emphasis>:
146 The <filename>poky-extras</filename> Git repository contains metadata needed to 159 The <filename>poky-extras</filename> Git repository contains metadata needed
147 build the kernel image. 160 only if you are modifying and building the kernel image.
148 In particular, it contains the kernel <filename>.bbappend</filename> files that you 161 In particular, it contains the kernel BitBake append (<filename>.bbappend</filename>)
162 files that you
149 edit to point to your locally modified kernel source files and to build the kernel 163 edit to point to your locally modified kernel source files and to build the kernel
150 image. 164 image.
151 Pointing to these local files is much more efficient than requiring a download of the 165 Pointing to these local files is much more efficient than requiring a download of the
152 source files from upstream each time you make changes to the kernel.</para> 166 source files from upstream each time you make changes to the kernel.</para>
153 <para>It is good practice to create this Git repository inside the Yocto Project 167 <para>You can find the <filename>poky-extras</filename> Git Repository in the
154 files Git repository. 168 "Yocto Metadata Layers" area of the Yocto Project Source Repositories at
155 Following is an example that creates the <filename>poky-extras</filename> Git 169 <ulink url='&YOCTO_GIT_URL;/cgit.cgi'></ulink>.
170 It is good practice to create this Git repository inside the Yocto Project
171 files Git repository.</para>
172 <para>Following is an example that creates the <filename>poky-extras</filename> Git
156 repository inside the Yocto Project files Git repository, which is named 173 repository inside the Yocto Project files Git repository, which is named
157 <filename>poky</filename> in this case: 174 <filename>poky</filename> in this case:
158 <literallayout class='monospaced'> 175 <literallayout class='monospaced'>
159 $ cd ~/poky
160 $ git clone git://git.yoctoproject.org/poky-extras poky-extras 176 $ git clone git://git.yoctoproject.org/poky-extras poky-extras
161 Initialized empty Git repository in /home/scottrif/poky/poky-extras/.git/ 177 Initialized empty Git repository in /home/scottrif/poky/poky-extras/.git/
162 remote: Counting objects: 561, done. 178 remote: Counting objects: 561, done.
@@ -169,6 +185,7 @@
169 Similar considerations exist for BSPs. 185 Similar considerations exist for BSPs.
170 You can get set up for BSP development one of two ways: tarball extraction or 186 You can get set up for BSP development one of two ways: tarball extraction or
171 with a local Git repository. 187 with a local Git repository.
188 It is a good idea to use the same method used to set up the Yocto Project Files.
172 Regardless of the method you use, the Yocto Project uses the following BSP layer 189 Regardless of the method you use, the Yocto Project uses the following BSP layer
173 naming scheme: 190 naming scheme:
174 <literallayout class='monospaced'> 191 <literallayout class='monospaced'>
@@ -184,21 +201,23 @@
184 <itemizedlist> 201 <itemizedlist>
185 <listitem><para><emphasis>Tarball Extraction:</emphasis> You can download any released 202 <listitem><para><emphasis>Tarball Extraction:</emphasis> You can download any released
186 BSP tarball from the same 203 BSP tarball from the same
187 <ulink url='http://yoctoproject.org/download'>download site</ulink> used 204 <ulink url='&YOCTO_HOME_URL;/download'>download site</ulink> used
188 to get the Yocto Project release. 205 to get the Yocto Project release.
189 Once you have the tarball, just extract it into a directory of your choice. 206 Once you have the tarball, just extract it into a directory of your choice.
190 Again, this method just produces a snapshot of the BSP layer in the form 207 Again, this method just produces a snapshot of the BSP layer in the form
191 of a hierarchical directory structure.</para></listitem> 208 of a hierarchical directory structure.</para></listitem>
192 <listitem><para><emphasis>Git Repository Method:</emphasis> If you are working 209 <listitem><para><emphasis>Git Repository Method:</emphasis> If you are working
193 with a Yocto Project files Git repository, you should also set up a 210 with a Yocto Project Files Git repository, you should also use this method
194 <filename>meta-intel</filename> Git repository. 211 to set up the <filename>meta-intel</filename> Git repository.
195 Typically, you set up the <filename>meta-intel</filename> Git repository inside 212 You can locate the <filename>meta-intel</filename> Git repository in the
196 the Yocto Project files Git repository.</para> 213 "Yocto Metadata Layers" area of the Yocto Project Source Repositories at
197 <para>For example, the following transcript shows the steps to clone the 214 <ulink url='&YOCTO_GIT_URL;/cgit.cgi'></ulink>.</para>
215 <para>Typically, you set up the <filename>meta-intel</filename> Git repository inside
216 the Yocto Project Files Git repository.
217 For example, the following transcript shows the steps to clone the
198 <filename>meta-intel</filename> 218 <filename>meta-intel</filename>
199 Git repository inside the <filename>poky</filename> Git repository. 219 Git repository inside the <filename>poky</filename> Git repository.
200 <literallayout class='monospaced'> 220 <literallayout class='monospaced'>
201 $cd poky
202 $ git clone git://git.yoctoproject.org/meta-intel.git 221 $ git clone git://git.yoctoproject.org/meta-intel.git
203 Initialized empty Git repository in /home/scottrif/poky/meta-intel/.git/ 222 Initialized empty Git repository in /home/scottrif/poky/meta-intel/.git/
204 remote: Counting objects: 3279, done. 223 remote: Counting objects: 3279, done.
@@ -208,7 +227,7 @@
208 Resolving deltas: 100% (1761/1761), done. 227 Resolving deltas: 100% (1761/1761), done.
209 </literallayout></para> 228 </literallayout></para>
210 <para>The same 229 <para>The same
211 <ulink url='https://wiki.yoctoproject.org/wiki/Transcript:_from_git_checkout_to_meta-intel_BSP'> 230 <ulink url='&YOCTO_WIKI_URL;/wiki/Transcript:_from_git_checkout_to_meta-intel_BSP'>
212 wiki page</ulink> referenced earlier covers how to 231 wiki page</ulink> referenced earlier covers how to
213 set up the <filename>meta-intel</filename> Git repository.</para></listitem> 232 set up the <filename>meta-intel</filename> Git repository.</para></listitem>
214 </itemizedlist></para></listitem> 233 </itemizedlist></para></listitem>
@@ -216,7 +235,7 @@
216 applications using the Eclipse Integrated Development Environment (IDE), 235 applications using the Eclipse Integrated Development Environment (IDE),
217 you will need this plug-in. 236 you will need this plug-in.
218 See the 237 See the
219 "<ulink url='http://www.yoctoproject.org/docs/1.1.1/adt-manual/adt-manual.html#setting-up-the-eclipse-ide'>Setting up the Eclipse IDE</ulink>" 238 "<ulink url='&YOCTO_DOCS_ADT_URL;#setting-up-the-eclipse-ide'>Setting up the Eclipse IDE</ulink>"
220 section in the Yocto Application Development Toolkit (ADT) 239 section in the Yocto Application Development Toolkit (ADT)
221 User’s Guide for more information.</para></listitem> 240 User’s Guide for more information.</para></listitem>
222 </itemizedlist> 241 </itemizedlist>
@@ -229,7 +248,7 @@
229 <para> 248 <para>
230 The build process creates an entire Linux distribution, including the toolchain, from source. 249 The build process creates an entire Linux distribution, including the toolchain, from source.
231 For more information on this topic, see the 250 For more information on this topic, see the
232 "<ulink url='http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html#building-image'>Building an Image</ulink>" 251 "<ulink url='&YOCTO_DOCS_QS_URL;#building-image'>Building an Image</ulink>"
233 section in the Yocto Project Quick Start. 252 section in the Yocto Project Quick Start.
234 </para> 253 </para>
235 254
@@ -240,12 +259,20 @@
240 previous section.</para></listitem> 259 previous section.</para></listitem>
241 <listitem><para>Initialize the build environment by sourcing a build environment 260 <listitem><para>Initialize the build environment by sourcing a build environment
242 script.</para></listitem> 261 script.</para></listitem>
243 <listitem><para>Optionally ensure the <filename>conf/local.conf</filename> configuration file is set 262 <listitem><para>Optionally ensure the <filename>/conf/local.conf</filename> configuration file,
244 up how you want it. 263 which is found in the Yocto Project build directory,
245 This file defines the target machine architecture and other build options.</para></listitem> 264 is set up how you want it.
246 <listitem><para>Build the image using the BitBake command. 265 This file defines many aspects of the build environment including
247 If you want information on Bitbake, see the user manual at 266 the target machine architecture through the
248 <ulink url='http://docs.openembedded.org/bitbake/html'></ulink>.</para></listitem> 267 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'>MACHINE</ulink></filename> variable,
268 the development machine's processor use through the
269 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-BB_NUMBER_THREADS'>BB_NUMBER_THREADS</ulink></filename> and
270 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PARALLEL_MAKE'>PARALLEL_MAKE</ulink></filename> variables, and
271 a centralized tarball download directory through the
272 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-DL_DIR'>DL_DIR</ulink></filename> variable.</para></listitem>
273 <listitem><para>Build the image using the <filename>bitbake</filename> command.
274 If you want information on BitBake, see the user manual at
275 <ulink url='&OE_DOCS_URL;/bitbake/html'></ulink>.</para></listitem>
249 <listitem><para>Run the image either on the actual hardware or using the QEMU 276 <listitem><para>Run the image either on the actual hardware or using the QEMU
250 emulator.</para></listitem> 277 emulator.</para></listitem>
251 </orderedlist> 278 </orderedlist>
@@ -256,18 +283,37 @@
256 <title>Using Pre-Built Binaries and QEMU</title> 283 <title>Using Pre-Built Binaries and QEMU</title>
257 284
258 <para> 285 <para>
259 Another option you have to get started is to use pre-built binaries. 286 Another option you have to get started is to use pre-built binaries.
260 This scenario is ideal for developing software applications to run on your target hardware. 287 The Yocto Project provides many types of binaries with each release.
261 To do this, you need to install the stand-alone Yocto Project cross-toolchain tarball and 288 See the <ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>
262 then download the pre-built kernel that you will boot in the QEMU emulator. 289 section for descriptions of the types of binaries that ship with a Yocto Project
263 Next, you must download and extract the target root filesystem for your target 290 release.
264 machine’s architecture. 291 </para>
265 Finally, you set up the environment to emulate the hardware and then start the QEMU emulator. 292
293 <para>
294 Using a pre-built binary is ideal for developing software applications to run on your
295 target hardware.
296 To do this, you need to be able to access the appropriate cross-toolchain tarball for
297 the architecture on which you are developing.
298 If you are using an SDK type image, the image ships with the complete toolchain native to
299 the architecture.
300 If you are not using an SDK type image, you need to separately download and
301 install the stand-alone Yocto Project cross-toolchain tarball.
266 </para> 302 </para>
267 303
268 <para> 304 <para>
305 Regardless of the type of image you are using, you need to download the pre-built kernel
306 that you will boot in the QEMU emulator and then download and extract the target root
307 filesystem for your target machine’s architecture.
308 You can get architecture-specific binaries and filesystem from
309 <ulink url='&YOCTO_MACHINES_DL_URL;'>machines</ulink>.
310 You can get stand-alone toolchains from
311 <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'>toolchains</ulink>.
312 Once you have all your files, you set up the environment to emulate the hardware
313 by sourcing an environment setup script.
314 Finally, you start the QEMU emulator.
269 You can find details on all these steps in the 315 You can find details on all these steps in the
270 "<ulink url='http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html#using-pre-built'>Using Pre-Built Binaries and QEMU</ulink>" 316 "<ulink url='&YOCTO_DOCS_QS_URL;#using-pre-built'>Using Pre-Built Binaries and QEMU</ulink>"
271 section of the Yocto Project Quick Start. 317 section of the Yocto Project Quick Start.
272 </para> 318 </para>
273</section> 319</section>