diff options
author | Timo Mueller <timo.mueller@bmw-carit.de> | 2013-02-08 09:16:33 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-02-14 17:25:35 +0000 |
commit | a41a805500cab281fba15bd8e5d3e60b88d0d4be (patch) | |
tree | 9973678912b57cfdef5b1f9676794a556b4d8966 /documentation/ref-manual/eclipse/html/poky-ref-manual/ref-images.html | |
parent | 768152340898cbb9faed6e8865a4e35c69833230 (diff) | |
download | poky-a41a805500cab281fba15bd8e5d3e60b88d0d4be.tar.gz |
documentation: Part 1 of 2 updates to integrating docs to Eclipse help.
Hi,
the generation of eclipse help files has been merged from the timo
branch to the master. Since the creation of the timo branch there have
been some changes to the master branch (e.g. new documentation,
renamed documentation).
This patch set does some cleanup for the renamed documentation and
adds eclipse help generation support to the new documentation.
01: Removes the 'the' from the document titles
02..04: Cleanup obsolete artifacts resulting from the merge
05..08: Add eclipse help generation for ref-manual
09..13: Add eclipse help generation for kernel-dev
14..18: Add eclipse help generation for profile-manual
Best regards,
Timo
This patch set originally contained 18 patches. I (Scott Rifenbark)
had to push these changes as two parts. This is the first part.
It does not include creation of the three cusomization files.
(From yocto-docs rev: 9b1889f6e31ee70dae704fa08763fb9196616dad)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/ref-images.html')
-rw-r--r-- | documentation/ref-manual/eclipse/html/poky-ref-manual/ref-images.html | 137 |
1 files changed, 0 insertions, 137 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-images.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-images.html deleted file mode 100644 index 81ed4ba8f2..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-images.html +++ /dev/null | |||
@@ -1,137 +0,0 @@ | |||
1 | <html> | ||
2 | <head> | ||
3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
4 | <title>Chapter 8. Images</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="The Yocto Project Reference Manual"> | ||
8 | <link rel="up" href="index.html" title="The Yocto Project Reference Manual"> | ||
9 | <link rel="prev" href="ref-classes-others.html" title="7.21. Other Classes"> | ||
10 | <link rel="next" href="ref-features.html" title="Chapter 9. Reference: Features"> | ||
11 | </head> | ||
12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 8. Images"> | ||
13 | <div class="titlepage"><div><div><h2 class="title"> | ||
14 | <a name="ref-images"></a>Chapter 8. Images</h2></div></div></div> | ||
15 | <p> | ||
16 | The OpenEmbedded build process supports several types of images to satisfy different needs. | ||
17 | When you issue the <code class="filename">bitbake</code> command you provide a “top-level” recipe | ||
18 | that essentially begins the build for the type of image you want. | ||
19 | </p> | ||
20 | <div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> | ||
21 | <h3 class="title">Note</h3> | ||
22 | Building an image without GNU General Public License Version 3 (GPLv3) components | ||
23 | is only supported for minimal and base images. | ||
24 | Furthermore, if you are going to build an image using non-GPLv3 components, | ||
25 | you must make the following changes in the <code class="filename">local.conf</code> file | ||
26 | before using the BitBake command to build the minimal or base image: | ||
27 | <pre class="literallayout"> | ||
28 | 1. Comment out the EXTRA_IMAGE_FEATURES line | ||
29 | 2. Set INCOMPATIBLE_LICENSE = "GPLv3" | ||
30 | </pre> | ||
31 | </div> | ||
32 | <p> | ||
33 | From within the <code class="filename">poky</code> Git repository, use the following command to list | ||
34 | the supported images: | ||
35 | </p> | ||
36 | <pre class="literallayout"> | ||
37 | $ ls meta*/recipes*/images/*.bb | ||
38 | </pre> | ||
39 | <p> | ||
40 | These recipes reside in the <code class="filename">meta/recipes-core/images</code>, | ||
41 | <code class="filename">meta/recipes-extended/images</code>, | ||
42 | <code class="filename">meta/recipes-graphics/images</code>, and | ||
43 | <code class="filename">meta/recipes-sato/images</code> directories | ||
44 | within the <a class="link" href="../dev-manual/source-directory.html" target="_self">source directory</a>. | ||
45 | Although the recipe names are somewhat explanatory, here is a list that describes them: | ||
46 | </p> | ||
47 | <div class="itemizedlist"><ul class="itemizedlist" type="disc"> | ||
48 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-base</code>:</em></span> | ||
49 | A console-only image that fully supports the target device hardware.</p></li> | ||
50 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-minimal</code>:</em></span> | ||
51 | A small image just capable of allowing a device to boot.</p></li> | ||
52 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-minimal-dev</code>:</em></span> | ||
53 | A <code class="filename">core-image-minimal</code> image suitable for development work | ||
54 | using the host. | ||
55 | The image includes headers and libraries you can use in a host development | ||
56 | environment. | ||
57 | </p></li> | ||
58 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-minimal-initramfs</code>:</em></span> | ||
59 | A <code class="filename">core-image-minimal</code> image that has the Minimal RAM-based | ||
60 | Initial Root Filesystem (<code class="filename">initramfs</code>) as part of the kernel, | ||
61 | which allows the system to find the first “init” program more efficiently. | ||
62 | </p></li> | ||
63 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-minimal-mtdutils</code>:</em></span> | ||
64 | A <code class="filename">core-image-minimal</code> image that has support | ||
65 | for the Minimal MTD Utilities, which let the user interact with the | ||
66 | MTD subsystem in the kernel to perform operations on flash devices. | ||
67 | </p></li> | ||
68 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-x11</code>:</em></span> | ||
69 | A very basic X11 image with a terminal. | ||
70 | </p></li> | ||
71 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-basic</code>:</em></span> | ||
72 | A console-only image with more full-featured Linux system | ||
73 | functionality installed.</p></li> | ||
74 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-lsb</code>:</em></span> | ||
75 | An image that conforms to the Linux Standard Base (LSB) specification.</p></li> | ||
76 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-lsb-dev</code>:</em></span> | ||
77 | A <code class="filename">core-image-lsb</code> image that is suitable for development work | ||
78 | using the host. | ||
79 | The image includes headers and libraries you can use in a host development | ||
80 | environment. | ||
81 | </p></li> | ||
82 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-lsb-sdk</code>:</em></span> | ||
83 | A <code class="filename">core-image-lsb</code> that includes everything in meta-toolchain | ||
84 | but also includes development headers and libraries to form a complete standalone SDK. | ||
85 | This image is suitable for development using the target.</p></li> | ||
86 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-clutter</code>:</em></span> | ||
87 | An image with support for the Open GL-based toolkit Clutter, which enables development of | ||
88 | rich and animated graphical user interfaces.</p></li> | ||
89 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-sato</code>:</em></span> | ||
90 | An image with Sato support, a mobile environment and visual style that works well | ||
91 | with mobile devices. | ||
92 | The image supports X11 with a Sato theme and applications such as | ||
93 | a terminal, editor, file manager, media player, and so forth.</p></li> | ||
94 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-sato-dev</code>:</em></span> | ||
95 | A <code class="filename">core-image-sato</code> image suitable for development | ||
96 | using the host. | ||
97 | The image includes libraries needed to build applications on the device itself, | ||
98 | testing and profiling tools, and debug symbols. | ||
99 | This image was formerly <code class="filename">core-image-sdk</code>.</p></li> | ||
100 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-sato-sdk</code>:</em></span> | ||
101 | A <code class="filename">core-image-sato</code> image that includes everything in meta-toolchain. | ||
102 | The image also includes development headers and libraries to form a complete standalone SDK | ||
103 | and is suitable for development using the target.</p></li> | ||
104 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-rt</code>:</em></span> | ||
105 | A <code class="filename">core-image-minimal</code> image plus a real-time test suite and | ||
106 | tools appropriate for real-time use.</p></li> | ||
107 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-rt-sdk</code>:</em></span> | ||
108 | A <code class="filename">core-image-rt</code> image that includes everything in | ||
109 | <code class="filename">meta-toolchain</code>. | ||
110 | The image also includes development headers and libraries to form a complete | ||
111 | stand-alone SDK and is suitable for development using the target.</p></li> | ||
112 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-gtk-directfb</code>:</em></span> | ||
113 | An image that uses <code class="filename">gtk+</code> over <code class="filename">directfb</code> | ||
114 | instead of X11. | ||
115 | In order to build, this image requires specific distro configuration that enables | ||
116 | <code class="filename">gtk</code> over <code class="filename">directfb</code>.</p></li> | ||
117 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">build-appliance-image</code>:</em></span> | ||
118 | An image you can boot and run using either the | ||
119 | <a class="ulink" href="http://www.vmware.com/products/player/overview.html" target="_self">VMware Player</a> | ||
120 | or <a class="ulink" href="http://www.vmware.com/products/workstation/overview.html" target="_self">VMware Workstation</a>. | ||
121 | For more information on this image, see the | ||
122 | <a class="ulink" href="http://www.yoctoproject.org/documentation/build-appliance" target="_self">Build Appliance</a> page on | ||
123 | the Yocto Project website.</p></li> | ||
124 | </ul></div> | ||
125 | <div class="tip" title="Tip" style="margin-left: 0.5in; margin-right: 0.5in;"> | ||
126 | <h3 class="title">Tip</h3> | ||
127 | From the Yocto Project release 1.1 onwards, <code class="filename">-live</code> and | ||
128 | <code class="filename">-directdisk</code> images have been replaced by a "live" | ||
129 | option in <code class="filename">IMAGE_FSTYPES</code> that will work with any image to produce an | ||
130 | image file that can be | ||
131 | copied directly to a CD or USB device and run as is. | ||
132 | To build a live image, simply add | ||
133 | "live" to <code class="filename">IMAGE_FSTYPES</code> within the <code class="filename">local.conf</code> | ||
134 | file or wherever appropriate and then build the desired image as normal. | ||
135 | </div> | ||
136 | </div></body> | ||
137 | </html> | ||