summaryrefslogtreecommitdiffstats
path: root/documentation/yocto-project-qs/yocto-project-qs.xml
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2017-07-26 12:04:48 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-07-30 16:23:51 +0100
commitf4aa9783bdd1b37aefb51b8cf55c3502bf031a4e (patch)
tree023232a0053a8f3714192cecb76199d432b68978 /documentation/yocto-project-qs/yocto-project-qs.xml
parent5a402f9d1b6d4b829bdabaa4cb1c57bc7db1684b (diff)
downloadpoky-f4aa9783bdd1b37aefb51b8cf55c3502bf031a4e.tar.gz
yocto-project-qs, ref-manual: Moved YP intro from QS to ref-manual
Fixes [YOCTO #11630] The introductory stuff in the QS is really conceptual information and needs to be in the ref-manual where YP is introduced. Regarding the QS, all we really need to do is point to places where the reader can go to find that stuff out. Part of this move involved getting the diagram of the YP flow for the environment from the QS to the ref-manual. That figure was named "YP-flow-diagram.png". It was named "yocto-environment.png" in the QS but I renamed it when moving it to the ref-manual. This caused some edits to the "Makefile" to clean up the figure lists for tarballs. (From yocto-docs rev: ab108c0959e3a9f36d25080245482f8a790c8c87) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/yocto-project-qs/yocto-project-qs.xml')
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml76
1 files changed, 0 insertions, 76 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index 9a4a14731f..f1b6728bd0 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -161,82 +161,6 @@
161 </para> 161 </para>
162 </section> 162 </section>
163 163
164 <section id='yp-intro'>
165 <title>Introducing the Yocto Project Development Environment</title>
166
167 <para>
168 The Yocto Project through the OpenEmbedded build system provides an
169 open source development environment targeting the ARM, MIPS,
170 PowerPC, and x86 architectures for a variety of platforms
171 including x86-64 and emulated ones.
172 You can use components from the Yocto Project to design, develop,
173 build, debug, simulate, and test the complete software stack using
174 Linux, the X Window System, GTK+ frameworks, and Qt frameworks.
175 </para>
176
177 <mediaobject>
178 <imageobject>
179 <imagedata fileref="figures/yocto-environment.png"
180 format="PNG" align='center' width="8in"/>
181 </imageobject>
182 </mediaobject>
183
184 <para>
185 Here are some highlights for the Yocto Project:
186 </para>
187
188 <itemizedlist>
189 <listitem><para>
190 Provides a recent Linux kernel along with a set of system
191 commands and libraries suitable for the embedded
192 environment.
193 </para></listitem>
194 <listitem><para>
195 Makes available system components such as X11, GTK+, Qt,
196 Clutter, and SDL (among others) so you can create a rich user
197 experience on devices that have display hardware.
198 For devices that do not have a display or where you wish to
199 use alternative UI frameworks, these components need not be
200 installed.
201 </para></listitem>
202 <listitem><para>
203 Creates a focused and stable core compatible with the
204 OpenEmbedded project with which you can easily and reliably
205 build and develop.
206 </para></listitem>
207 <listitem><para>
208 Fully supports a wide range of hardware and device emulation
209 through the Quick EMUlator (QEMU).
210 </para></listitem>
211 <listitem><para>
212 Provides a layer mechanism that allows you to easily extend
213 the system, make customizations, and keep them organized.
214 </para></listitem>
215 </itemizedlist>
216
217 <para>
218 You can use the Yocto Project to generate images for many kinds
219 of devices.
220 As mentioned earlier, the Yocto Project supports creation of
221 reference images that you can boot within and emulate using QEMU.
222 The standard example machines target QEMU full-system
223 emulation for 32-bit and 64-bit variants of x86, ARM, MIPS, and
224 PowerPC architectures.
225 Beyond emulation, you can use the layer mechanism to extend
226 support to just about any platform that Linux can run on and that
227 a toolchain can target.
228 </para>
229
230 <para>
231 Another Yocto Project feature is the Sato reference User
232 Interface.
233 This optional UI that is based on GTK+ is intended for devices with
234 restricted screen sizes and is included as part of the
235 OpenEmbedded Core layer so that developers can test parts of the
236 software stack.
237 </para>
238 </section>
239
240 <section id='yp-resources'> 164 <section id='yp-resources'>
241 <title>Setting Up to Use the Yocto Project</title> 165 <title>Setting Up to Use the Yocto Project</title>
242 166