diff options
Diffstat (limited to 'documentation/getting-started/eclipse/html/getting-started/yp-intro.html')
| -rw-r--r-- | documentation/getting-started/eclipse/html/getting-started/yp-intro.html | 119 |
1 files changed, 119 insertions, 0 deletions
diff --git a/documentation/getting-started/eclipse/html/getting-started/yp-intro.html b/documentation/getting-started/eclipse/html/getting-started/yp-intro.html new file mode 100644 index 0000000000..42ad0d3088 --- /dev/null +++ b/documentation/getting-started/eclipse/html/getting-started/yp-intro.html | |||
| @@ -0,0 +1,119 @@ | |||
| 1 | <html> | ||
| 2 | <head> | ||
| 3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
| 4 | <title>2.1. Introduction</title> | ||
| 5 | <link rel="stylesheet" type="text/css" href="../book.css"> | ||
| 6 | <meta name="generator" content="DocBook XSL Stylesheets V1.76.1"> | ||
| 7 | <link rel="home" href="index.html" title="Getting Started With Yocto Project"> | ||
| 8 | <link rel="up" href="overview-development-environment.html" title="Chapter 2. The Yocto Project Development Environment"> | ||
| 9 | <link rel="prev" href="overview-development-environment.html" title="Chapter 2. The Yocto Project Development Environment"> | ||
| 10 | <link rel="next" href="open-source-philosophy.html" title="2.2. Open Source Philosophy"> | ||
| 11 | </head> | ||
| 12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.1. Introduction"> | ||
| 13 | <div class="titlepage"><div><div><h2 class="title" style="clear: both"> | ||
| 14 | <a name="yp-intro"></a>2.1. Introduction</h2></div></div></div> | ||
| 15 | <p> | ||
| 16 | The Yocto Project is an open-source collaboration project whose | ||
| 17 | focus is for developers of embedded Linux systems. | ||
| 18 | Among other things, the Yocto Project uses an | ||
| 19 | <a class="link" href="../ref-manual/build-system-term.html" target="_self">OpenEmbedded build system</a>. | ||
| 20 | The build system, which is based on the OpenEmbedded (OE) project and | ||
| 21 | uses the | ||
| 22 | <a class="link" href="../ref-manual/bitbake-term.html" target="_self">BitBake</a> tool, | ||
| 23 | constructs complete Linux images for architectures based on ARM, MIPS, | ||
| 24 | PowerPC, x86 and x86-64. | ||
| 25 | </p> | ||
| 26 | <div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> | ||
| 27 | <h3 class="title">Note</h3> | ||
| 28 | Historically, the OpenEmbedded build system, which is the | ||
| 29 | combination of BitBake and OE components, formed a reference | ||
| 30 | build host that was known as | ||
| 31 | "<a class="link" href="../ref-manual/poky.html" target="_self">Poky</a>" | ||
| 32 | (<span class="emphasis"><em>Pah</em></span>-kee). | ||
| 33 | The term "Poky", as used throughout the Yocto Project Documentation | ||
| 34 | set, can have different meanings. | ||
| 35 | </div> | ||
| 36 | <p> | ||
| 37 | The Yocto Project provides various ancillary tools for the embedded | ||
| 38 | developer and also features the Sato reference User Interface, which | ||
| 39 | is optimized for stylus-driven, low-resolution screens. | ||
| 40 | </p> | ||
| 41 | <div class="mediaobject" align="center"><table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="720"><tr><td align="center"><img src="figures/YP-flow-diagram.png" align="middle" width="720"></td></tr></table></div> | ||
| 42 | <p> | ||
| 43 | Here are some highlights for the Yocto Project: | ||
| 44 | </p> | ||
| 45 | <div class="itemizedlist"><ul class="itemizedlist" type="disc"> | ||
| 46 | <li class="listitem"><p> | ||
| 47 | Provides a recent Linux kernel along with a set of system | ||
| 48 | commands and libraries suitable for the embedded | ||
| 49 | environment. | ||
| 50 | </p></li> | ||
| 51 | <li class="listitem"><p> | ||
| 52 | Makes available system components such as X11, GTK+, Qt, | ||
| 53 | Clutter, and SDL (among others) so you can create a rich user | ||
| 54 | experience on devices that have display hardware. | ||
| 55 | For devices that do not have a display or where you wish to | ||
| 56 | use alternative UI frameworks, these components need not be | ||
| 57 | installed. | ||
| 58 | </p></li> | ||
| 59 | <li class="listitem"><p> | ||
| 60 | Creates a focused and stable core compatible with the | ||
| 61 | OpenEmbedded project with which you can easily and reliably | ||
| 62 | build and develop. | ||
| 63 | </p></li> | ||
| 64 | <li class="listitem"><p> | ||
| 65 | Fully supports a wide range of hardware and device emulation | ||
| 66 | through the Quick EMUlator (QEMU). | ||
| 67 | </p></li> | ||
| 68 | <li class="listitem"><p> | ||
| 69 | Provides a layer mechanism that allows you to easily extend | ||
| 70 | the system, make customizations, and keep them organized. | ||
| 71 | </p></li> | ||
| 72 | </ul></div> | ||
| 73 | <p> | ||
| 74 | You can use the Yocto Project to generate images for many kinds | ||
| 75 | of devices. | ||
| 76 | As mentioned earlier, the Yocto Project supports creation of | ||
| 77 | reference images that you can boot within and emulate using QEMU. | ||
| 78 | The standard example machines target QEMU full-system | ||
| 79 | emulation for 32-bit and 64-bit variants of x86, ARM, MIPS, and | ||
| 80 | PowerPC architectures. | ||
| 81 | Beyond emulation, you can use the layer mechanism to extend | ||
| 82 | support to just about any platform that Linux can run on and that | ||
| 83 | a toolchain can target. | ||
| 84 | </p> | ||
| 85 | <p> | ||
| 86 | Another Yocto Project feature is the Sato reference User | ||
| 87 | Interface. | ||
| 88 | This optional UI that is based on GTK+ is intended for devices with | ||
| 89 | restricted screen sizes and is included as part of the | ||
| 90 | OpenEmbedded Core layer so that developers can test parts of the | ||
| 91 | software stack. | ||
| 92 | </p> | ||
| 93 | <p> | ||
| 94 | While the Yocto Project does not provide a strict testing framework, | ||
| 95 | it does provide or generate for you artifacts that let you perform | ||
| 96 | target-level and emulated testing and debugging. | ||
| 97 | Additionally, if you are an | ||
| 98 | <span class="trademark">Eclipse</span>™ IDE user, you can | ||
| 99 | install an Eclipse Yocto Plug-in to allow you to develop within that | ||
| 100 | familiar environment. | ||
| 101 | </p> | ||
| 102 | <p> | ||
| 103 | By default, using the Yocto Project to build an image creates a Poky | ||
| 104 | distribution. | ||
| 105 | However, you can create your own distribution by providing key | ||
| 106 | <a class="link" href="../ref-manual/metadata.html" target="_self">Metadata</a>. | ||
| 107 | A good example is Angstrom, which has had a distribution | ||
| 108 | based on the Yocto Project since its inception. | ||
| 109 | Other examples include commercial distributions like | ||
| 110 | <a class="ulink" href="https://www.yoctoproject.org/organization/wind-river-systems" target="_self">Wind River Linux</a>, | ||
| 111 | <a class="ulink" href="https://www.yoctoproject.org/organization/mentor-graphics" target="_self">Mentor Embedded Linux</a>, | ||
| 112 | <a class="ulink" href="https://www.yoctoproject.org/organization/enea-ab" target="_self">ENEA Linux</a> | ||
| 113 | and <a class="ulink" href="https://www.yoctoproject.org/ecosystem/member-organizations" target="_self">others</a>. | ||
| 114 | See the "<a class="link" href="../dev-manual/creating-your-own-distribution.html" target="_self">Creating Your Own Distribution</a>" | ||
| 115 | section in the Yocto Project Development Tasks Manual for more | ||
| 116 | information. | ||
| 117 | </p> | ||
| 118 | </div></body> | ||
| 119 | </html> | ||