1 files changed, 1 insertions, 119 deletions
diff --git a/documentation/getting-started/getting-started-development-environment.xml b/documentation/getting-started/getting-started-development-environment.xml
index 5d6491c51b..54a607f6ab 100644
--- a/documentation/getting-started/getting-started-development-environment.xml
+++ b/documentation/getting-started/getting-started-development-environment.xml
@@ -7,8 +7,7 @@
 <para>
    This chapter takes a look at the Yocto Project development
-    environment and also provides a detailed look at what goes on during
+    environment.
-    development in that environment.
    The chapter provides Yocto Project Development environment concepts that
    help you understand how work is accomplished in an open source environment,
    which is very different as compared to work accomplished in a closed,
@@ -21,123 +20,6 @@
    syntax.
 </para>
-<section id='yp-intro'>
-    <title>Introduction</title>
-    <para>
-        The Yocto Project is an open-source collaboration project whose
-        focus is for developers of embedded Linux systems.
-        Among other things, the Yocto Project uses an
-        <ulink url='&YOCTO_DOCS_REF_URL;#build-system-term'>OpenEmbedded build system</ulink>.
-        The build system, which is based on the OpenEmbedded (OE) project and
-        uses the
-        <ulink url='&YOCTO_DOCS_REF_URL;#bitbake-term'>BitBake</ulink> tool,
-        constructs complete Linux images for architectures based on ARM, MIPS,
-        PowerPC, x86 and x86-64.
-        <note>
-            Historically, the OpenEmbedded build system, which is the
-            combination of BitBake and OE components, formed a reference
-            build host that was known as
-            "<ulink url='&YOCTO_DOCS_REF_URL;#poky'>Poky</ulink>"
-            (<emphasis>Pah</emphasis>-kee).
-            The term "Poky", as used throughout the Yocto Project Documentation
-            set, can have different meanings.
-        </note>
-        The Yocto Project provides various ancillary tools for the embedded
-        developer and also features the Sato reference User Interface, which
-        is optimized for stylus-driven, low-resolution screens.
-    </para>
-    <mediaobject>
-        <imageobject>
-            <imagedata fileref="figures/YP-flow-diagram.png"
-                format="PNG" align='center' width="8in"/>
-        </imageobject>
-    </mediaobject>
-    <para>
-        Here are some highlights for the Yocto Project:
-    </para>
-    <itemizedlist>
-        <listitem><para>
-            Provides a recent Linux kernel along with a set of system
-            commands and libraries suitable for the embedded
-            environment.
-            </para></listitem>
-        <listitem><para>
-            Makes available system components such as X11, GTK+, Qt,
-            Clutter, and SDL (among others) so you can create a rich user
-            experience on devices that have display hardware.
-            For devices that do not have a display or where you wish to
-            use alternative UI frameworks, these components need not be
-            installed.
-            </para></listitem>
-        <listitem><para>
-            Creates a focused and stable core compatible with the
-            OpenEmbedded project with which you can easily and reliably
-            build and develop.
-            </para></listitem>
-        <listitem><para>
-            Fully supports a wide range of hardware and device emulation
-            through the Quick EMUlator (QEMU).
-            </para></listitem>
-        <listitem><para>
-            Provides a layer mechanism that allows you to easily extend
-            the system, make customizations, and keep them organized.
-            </para></listitem>
-    </itemizedlist>
-    <para>
-        You can use the Yocto Project to generate images for many kinds
-        of devices.
-        As mentioned earlier, the Yocto Project supports creation of
-        reference images that you can boot within and emulate using QEMU.
-        The standard example machines target QEMU full-system
-        emulation for 32-bit and 64-bit variants of x86, ARM, MIPS, and
-        PowerPC architectures.
-        Beyond emulation, you can use the layer mechanism to extend
-        support to just about any platform that Linux can run on and that
-        a toolchain can target.
-    </para>
-    <para>
-        Another Yocto Project feature is the Sato reference User
-        Interface.
-        This optional UI that is based on GTK+ is intended for devices with
-        restricted screen sizes and is included as part of the
-        OpenEmbedded Core layer so that developers can test parts of the
-        software stack.
-    </para>
-    <para>
-        While the Yocto Project does not provide a strict testing framework,
-        it does provide or generate for you artifacts that let you perform
-        target-level and emulated testing and debugging.
-        Additionally, if you are an
-        <trademark class='trade'>Eclipse</trademark> IDE user, you can
-        install an Eclipse Yocto Plug-in to allow you to develop within that
-        familiar environment.
-    </para>
-    <para>
-        By default, using the Yocto Project to build an image creates a Poky
-        distribution.
-        However, you can create your own distribution by providing key
-        <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>.
-        A good example is Angstrom, which has had a distribution
-        based on the Yocto Project since its inception.
-        Other examples include commercial distributions like
-        <ulink url='https://www.yoctoproject.org/organization/wind-river-systems'>Wind River Linux</ulink>,
-        <ulink url='https://www.yoctoproject.org/organization/mentor-graphics'>Mentor Embedded Linux</ulink>,
-        <ulink url='https://www.yoctoproject.org/organization/enea-ab'>ENEA Linux</ulink>
-        and <ulink url='https://www.yoctoproject.org/ecosystem/member-organizations'>others</ulink>.
-        See the "<ulink url='&YOCTO_DOCS_DEV_URL;#creating-your-own-distribution'>Creating Your Own Distribution</ulink>"
-        section in the Yocto Project Development Tasks Manual for more
-        information.
-    </para>
-</section>
 <section id='open-source-philosophy'>
    <title>Open Source Philosophy</title>

diff --git a/documentation/getting-started/getting-started-development-environment.xml b/documentation/getting-started/getting-started-development-environment.xml index 5d6491c51b..54a607f6ab 100644 --- a/documentation/getting-started/getting-started-development-environment.xml +++ b/documentation/getting-started/getting-started-development-environment.xml
@@ -7,8 +7,7 @@
7		7
8	<para>	8	<para>
9	This chapter takes a look at the Yocto Project development	9	This chapter takes a look at the Yocto Project development
10	environment and also provides a detailed look at what goes on during	10	environment.
11	development in that environment.
12	The chapter provides Yocto Project Development environment concepts that	11	The chapter provides Yocto Project Development environment concepts that
13	help you understand how work is accomplished in an open source environment,	12	help you understand how work is accomplished in an open source environment,
14	which is very different as compared to work accomplished in a closed,	13	which is very different as compared to work accomplished in a closed,
@@ -21,123 +20,6 @@
21	syntax.	20	syntax.
22	</para>	21	</para>
23		22
24	<section id='yp-intro'>
25	<title>Introduction</title>
26
27	<para>
28	The Yocto Project is an open-source collaboration project whose
29	focus is for developers of embedded Linux systems.
30	Among other things, the Yocto Project uses an
31	<ulink url='&YOCTO_DOCS_REF_URL;#build-system-term'>OpenEmbedded build system</ulink>.
32	The build system, which is based on the OpenEmbedded (OE) project and
33	uses the
34	<ulink url='&YOCTO_DOCS_REF_URL;#bitbake-term'>BitBake</ulink> tool,
35	constructs complete Linux images for architectures based on ARM, MIPS,
36	PowerPC, x86 and x86-64.
37	<note>
38	Historically, the OpenEmbedded build system, which is the
39	combination of BitBake and OE components, formed a reference
40	build host that was known as
41	"<ulink url='&YOCTO_DOCS_REF_URL;#poky'>Poky</ulink>"
42	(<emphasis>Pah</emphasis>-kee).
43	The term "Poky", as used throughout the Yocto Project Documentation
44	set, can have different meanings.
45	</note>
46	The Yocto Project provides various ancillary tools for the embedded
47	developer and also features the Sato reference User Interface, which
48	is optimized for stylus-driven, low-resolution screens.
49	</para>
50
51	<mediaobject>
52	<imageobject>
53	<imagedata fileref="figures/YP-flow-diagram.png"
54	format="PNG" align='center' width="8in"/>
55	</imageobject>
56	</mediaobject>
57
58	<para>
59	Here are some highlights for the Yocto Project:
60	</para>
61
62	<itemizedlist>
63	<listitem><para>
64	Provides a recent Linux kernel along with a set of system
65	commands and libraries suitable for the embedded
66	environment.
67	</para></listitem>
68	<listitem><para>
69	Makes available system components such as X11, GTK+, Qt,
70	Clutter, and SDL (among others) so you can create a rich user
71	experience on devices that have display hardware.
72	For devices that do not have a display or where you wish to
73	use alternative UI frameworks, these components need not be
74	installed.
75	</para></listitem>
76	<listitem><para>
77	Creates a focused and stable core compatible with the
78	OpenEmbedded project with which you can easily and reliably
79	build and develop.
80	</para></listitem>
81	<listitem><para>
82	Fully supports a wide range of hardware and device emulation
83	through the Quick EMUlator (QEMU).
84	</para></listitem>
85	<listitem><para>
86	Provides a layer mechanism that allows you to easily extend
87	the system, make customizations, and keep them organized.
88	</para></listitem>
89	</itemizedlist>
90
91	<para>
92	You can use the Yocto Project to generate images for many kinds
93	of devices.
94	As mentioned earlier, the Yocto Project supports creation of
95	reference images that you can boot within and emulate using QEMU.
96	The standard example machines target QEMU full-system
97	emulation for 32-bit and 64-bit variants of x86, ARM, MIPS, and
98	PowerPC architectures.
99	Beyond emulation, you can use the layer mechanism to extend
100	support to just about any platform that Linux can run on and that
101	a toolchain can target.
102	</para>
103
104	<para>
105	Another Yocto Project feature is the Sato reference User
106	Interface.
107	This optional UI that is based on GTK+ is intended for devices with
108	restricted screen sizes and is included as part of the
109	OpenEmbedded Core layer so that developers can test parts of the
110	software stack.
111	</para>
112
113	<para>
114	While the Yocto Project does not provide a strict testing framework,
115	it does provide or generate for you artifacts that let you perform
116	target-level and emulated testing and debugging.
117	Additionally, if you are an
118	<trademark class='trade'>Eclipse</trademark> IDE user, you can
119	install an Eclipse Yocto Plug-in to allow you to develop within that
120	familiar environment.
121	</para>
122
123	<para>
124	By default, using the Yocto Project to build an image creates a Poky
125	distribution.
126	However, you can create your own distribution by providing key
127	<ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>.
128	A good example is Angstrom, which has had a distribution
129	based on the Yocto Project since its inception.
130	Other examples include commercial distributions like
131	<ulink url='https://www.yoctoproject.org/organization/wind-river-systems'>Wind River Linux</ulink>,
132	<ulink url='https://www.yoctoproject.org/organization/mentor-graphics'>Mentor Embedded Linux</ulink>,
133	<ulink url='https://www.yoctoproject.org/organization/enea-ab'>ENEA Linux</ulink>
134	and <ulink url='https://www.yoctoproject.org/ecosystem/member-organizations'>others</ulink>.
135	See the "<ulink url='&YOCTO_DOCS_DEV_URL;#creating-your-own-distribution'>Creating Your Own Distribution</ulink>"
136	section in the Yocto Project Development Tasks Manual for more
137	information.
138	</para>
139	</section>
140
141	<section id='open-source-philosophy'>	23	<section id='open-source-philosophy'>
142	<title>Open Source Philosophy</title>	24	<title>Open Source Philosophy</title>
143		25