diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-12-07 17:29:51 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-12-11 16:17:56 +0000 |
commit | 73ffb8298b545a1a1fb96bc5952b7365c4c43bfd (patch) | |
tree | 9c6473cb4e3c5dd8370c2d417c304e1a302fa643 /documentation/poky-ref-manual/ref-images.xml | |
parent | acb3f72afaa28ba5d23ca6e5cdf9f1162ea656a3 (diff) | |
download | poky-73ffb8298b545a1a1fb96bc5952b7365c4c43bfd.tar.gz |
Documentation: poky-ref-manual - Removed all trailing whitespace.
(From yocto-docs rev: 564a28c2501034ea7e2eb16afc43dfaf931b6f6f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/poky-ref-manual/ref-images.xml')
-rw-r--r-- | documentation/poky-ref-manual/ref-images.xml | 66 |
1 files changed, 33 insertions, 33 deletions
diff --git a/documentation/poky-ref-manual/ref-images.xml b/documentation/poky-ref-manual/ref-images.xml index 79f2409933..0a827ca235 100644 --- a/documentation/poky-ref-manual/ref-images.xml +++ b/documentation/poky-ref-manual/ref-images.xml | |||
@@ -6,8 +6,8 @@ | |||
6 | <title>Images</title> | 6 | <title>Images</title> |
7 | 7 | ||
8 | <para> | 8 | <para> |
9 | The OpenEmbedded build process supports several types of images to satisfy different needs. | 9 | The OpenEmbedded build process supports several types of images to satisfy different needs. |
10 | When you issue the <filename>bitbake</filename> command you provide a “top-level” recipe | 10 | When you issue the <filename>bitbake</filename> command you provide a “top-level” recipe |
11 | that essentially begins the build for the type of image you want. | 11 | that essentially begins the build for the type of image you want. |
12 | </para> | 12 | </para> |
13 | 13 | ||
@@ -24,16 +24,16 @@ | |||
24 | </note> | 24 | </note> |
25 | 25 | ||
26 | <para> | 26 | <para> |
27 | From within the <filename>poky</filename> Git repository, use the following command to list | 27 | From within the <filename>poky</filename> Git repository, use the following command to list |
28 | the supported images: | 28 | the supported images: |
29 | <literallayout class='monospaced'> | 29 | <literallayout class='monospaced'> |
30 | $ ls meta*/recipes*/images/*.bb | 30 | $ ls meta*/recipes*/images/*.bb |
31 | </literallayout> | 31 | </literallayout> |
32 | These recipes reside in the <filename>meta/recipes-core/images</filename>, | 32 | These recipes reside in the <filename>meta/recipes-core/images</filename>, |
33 | <filename>meta/recipes-extended/images</filename>, | 33 | <filename>meta/recipes-extended/images</filename>, |
34 | <filename>meta/recipes-graphics/images</filename>, and | 34 | <filename>meta/recipes-graphics/images</filename>, and |
35 | <filename>meta/recipes-sato/images</filename> directories | 35 | <filename>meta/recipes-sato/images</filename> directories |
36 | within the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. | 36 | within the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. |
37 | Although the recipe names are somewhat explanatory, here is a list that describes them: | 37 | Although the recipe names are somewhat explanatory, here is a list that describes them: |
38 | </para> | 38 | </para> |
39 | 39 | ||
@@ -45,17 +45,17 @@ | |||
45 | <listitem><para><emphasis><filename>core-image-minimal-dev</filename>:</emphasis> | 45 | <listitem><para><emphasis><filename>core-image-minimal-dev</filename>:</emphasis> |
46 | A <filename>core-image-minimal</filename> image suitable for development work | 46 | A <filename>core-image-minimal</filename> image suitable for development work |
47 | using the host. | 47 | using the host. |
48 | The image includes headers and libraries you can use in a host development | 48 | The image includes headers and libraries you can use in a host development |
49 | environment. | 49 | environment. |
50 | </para></listitem> | 50 | </para></listitem> |
51 | <listitem><para><emphasis><filename>core-image-minimal-initramfs</filename>:</emphasis> | 51 | <listitem><para><emphasis><filename>core-image-minimal-initramfs</filename>:</emphasis> |
52 | A <filename>core-image-minimal</filename> image that has the Minimal RAM-based | 52 | A <filename>core-image-minimal</filename> image that has the Minimal RAM-based |
53 | Initial Root Filesystem (<filename>initramfs</filename>) as part of the kernel, | 53 | Initial Root Filesystem (<filename>initramfs</filename>) as part of the kernel, |
54 | which allows the system to find the first “init” program more efficiently. | 54 | which allows the system to find the first “init” program more efficiently. |
55 | </para></listitem> | 55 | </para></listitem> |
56 | <listitem><para><emphasis><filename>core-image-minimal-mtdutils</filename>:</emphasis> | 56 | <listitem><para><emphasis><filename>core-image-minimal-mtdutils</filename>:</emphasis> |
57 | A <filename>core-image-minimal</filename> image that has support | 57 | A <filename>core-image-minimal</filename> image that has support |
58 | for the Minimal MTD Utilities, which let the user interact with the | 58 | for the Minimal MTD Utilities, which let the user interact with the |
59 | MTD subsystem in the kernel to perform operations on flash devices. | 59 | MTD subsystem in the kernel to perform operations on flash devices. |
60 | </para></listitem> | 60 | </para></listitem> |
61 | <listitem><para><emphasis><filename>core-image-x11</filename>:</emphasis> | 61 | <listitem><para><emphasis><filename>core-image-x11</filename>:</emphasis> |
@@ -69,64 +69,64 @@ | |||
69 | <listitem><para><emphasis><filename>core-image-lsb-dev</filename>:</emphasis> | 69 | <listitem><para><emphasis><filename>core-image-lsb-dev</filename>:</emphasis> |
70 | A <filename>core-image-lsb</filename> image that is suitable for development work | 70 | A <filename>core-image-lsb</filename> image that is suitable for development work |
71 | using the host. | 71 | using the host. |
72 | The image includes headers and libraries you can use in a host development | 72 | The image includes headers and libraries you can use in a host development |
73 | environment. | 73 | environment. |
74 | </para></listitem> | 74 | </para></listitem> |
75 | <listitem><para><emphasis><filename>core-image-lsb-sdk</filename>:</emphasis> | 75 | <listitem><para><emphasis><filename>core-image-lsb-sdk</filename>:</emphasis> |
76 | A <filename>core-image-lsb</filename> that includes everything in meta-toolchain | 76 | A <filename>core-image-lsb</filename> that includes everything in meta-toolchain |
77 | but also includes development headers and libraries to form a complete standalone SDK. | 77 | but also includes development headers and libraries to form a complete standalone SDK. |
78 | This image is suitable for development using the target.</para></listitem> | 78 | This image is suitable for development using the target.</para></listitem> |
79 | <listitem><para><emphasis><filename>core-image-clutter</filename>:</emphasis> | 79 | <listitem><para><emphasis><filename>core-image-clutter</filename>:</emphasis> |
80 | An image with support for the Open GL-based toolkit Clutter, which enables development of | 80 | An image with support for the Open GL-based toolkit Clutter, which enables development of |
81 | rich and animated graphical user interfaces.</para></listitem> | 81 | rich and animated graphical user interfaces.</para></listitem> |
82 | <listitem><para><emphasis><filename>core-image-sato</filename>:</emphasis> | 82 | <listitem><para><emphasis><filename>core-image-sato</filename>:</emphasis> |
83 | An image with Sato support, a mobile environment and visual style that works well | 83 | An image with Sato support, a mobile environment and visual style that works well |
84 | with mobile devices. | 84 | with mobile devices. |
85 | The image supports X11 with a Sato theme and applications such as | 85 | The image supports X11 with a Sato theme and applications such as |
86 | a terminal, editor, file manager, media player, and so forth.</para></listitem> | 86 | a terminal, editor, file manager, media player, and so forth.</para></listitem> |
87 | <listitem><para><emphasis><filename>core-image-sato-dev</filename>:</emphasis> | 87 | <listitem><para><emphasis><filename>core-image-sato-dev</filename>:</emphasis> |
88 | A <filename>core-image-sato</filename> image suitable for development | 88 | A <filename>core-image-sato</filename> image suitable for development |
89 | using the host. | 89 | using the host. |
90 | The image includes libraries needed to build applications on the device itself, | 90 | The image includes libraries needed to build applications on the device itself, |
91 | testing and profiling tools, and debug symbols. | 91 | testing and profiling tools, and debug symbols. |
92 | This image was formerly <filename>core-image-sdk</filename>.</para></listitem> | 92 | This image was formerly <filename>core-image-sdk</filename>.</para></listitem> |
93 | <listitem><para><emphasis><filename>core-image-sato-sdk</filename>:</emphasis> | 93 | <listitem><para><emphasis><filename>core-image-sato-sdk</filename>:</emphasis> |
94 | A <filename>core-image-sato</filename> image that includes everything in meta-toolchain. | 94 | A <filename>core-image-sato</filename> image that includes everything in meta-toolchain. |
95 | The image also includes development headers and libraries to form a complete standalone SDK | 95 | The image also includes development headers and libraries to form a complete standalone SDK |
96 | and is suitable for development using the target.</para></listitem> | 96 | and is suitable for development using the target.</para></listitem> |
97 | <listitem><para><emphasis><filename>core-image-rt</filename>:</emphasis> | 97 | <listitem><para><emphasis><filename>core-image-rt</filename>:</emphasis> |
98 | A <filename>core-image-minimal</filename> image plus a real-time test suite and | 98 | A <filename>core-image-minimal</filename> image plus a real-time test suite and |
99 | tools appropriate for real-time use.</para></listitem> | 99 | tools appropriate for real-time use.</para></listitem> |
100 | <listitem><para><emphasis><filename>core-image-rt-sdk</filename>:</emphasis> | 100 | <listitem><para><emphasis><filename>core-image-rt-sdk</filename>:</emphasis> |
101 | A <filename>core-image-rt</filename> image that includes everything in | 101 | A <filename>core-image-rt</filename> image that includes everything in |
102 | <filename>meta-toolchain</filename>. | 102 | <filename>meta-toolchain</filename>. |
103 | The image also includes development headers and libraries to form a complete | 103 | The image also includes development headers and libraries to form a complete |
104 | stand-alone SDK and is suitable for development using the target.</para></listitem> | 104 | stand-alone SDK and is suitable for development using the target.</para></listitem> |
105 | <listitem><para><emphasis><filename>core-image-gtk-directfb</filename>:</emphasis> | 105 | <listitem><para><emphasis><filename>core-image-gtk-directfb</filename>:</emphasis> |
106 | An image that uses <filename>gtk+</filename> over <filename>directfb</filename> | 106 | An image that uses <filename>gtk+</filename> over <filename>directfb</filename> |
107 | instead of X11. | 107 | instead of X11. |
108 | In order to build, this image requires specific distro configuration that enables | 108 | In order to build, this image requires specific distro configuration that enables |
109 | <filename>gtk</filename> over <filename>directfb</filename>.</para></listitem> | 109 | <filename>gtk</filename> over <filename>directfb</filename>.</para></listitem> |
110 | <listitem><para><emphasis><filename>build-appliance-image</filename>:</emphasis> | 110 | <listitem><para><emphasis><filename>build-appliance-image</filename>:</emphasis> |
111 | An image you can boot and run using either the | 111 | An image you can boot and run using either the |
112 | <ulink url='http://www.vmware.com/products/player/overview.html'>VMware Player</ulink> | 112 | <ulink url='http://www.vmware.com/products/player/overview.html'>VMware Player</ulink> |
113 | or <ulink url='http://www.vmware.com/products/workstation/overview.html'>VMware Workstation</ulink>. | 113 | or <ulink url='http://www.vmware.com/products/workstation/overview.html'>VMware Workstation</ulink>. |
114 | For more information on this image, see the | 114 | For more information on this image, see the |
115 | <ulink url='&YOCTO_HOME_URL;/documentation/build-appliance'>Build Appliance</ulink> page on | 115 | <ulink url='&YOCTO_HOME_URL;/documentation/build-appliance'>Build Appliance</ulink> page on |
116 | the Yocto Project website.</para></listitem> | 116 | the Yocto Project website.</para></listitem> |
117 | </itemizedlist> | 117 | </itemizedlist> |
118 | 118 | ||
119 | <tip> | 119 | <tip> |
120 | From the Yocto Project release 1.1 onwards, <filename>-live</filename> and | 120 | From the Yocto Project release 1.1 onwards, <filename>-live</filename> and |
121 | <filename>-directdisk</filename> images have been replaced by a "live" | 121 | <filename>-directdisk</filename> images have been replaced by a "live" |
122 | option in <filename>IMAGE_FSTYPES</filename> that will work with any image to produce an | 122 | option in <filename>IMAGE_FSTYPES</filename> that will work with any image to produce an |
123 | image file that can be | 123 | image file that can be |
124 | copied directly to a CD or USB device and run as is. | 124 | copied directly to a CD or USB device and run as is. |
125 | To build a live image, simply add | 125 | To build a live image, simply add |
126 | "live" to <filename>IMAGE_FSTYPES</filename> within the <filename>local.conf</filename> | 126 | "live" to <filename>IMAGE_FSTYPES</filename> within the <filename>local.conf</filename> |
127 | file or wherever appropriate and then build the desired image as normal. | 127 | file or wherever appropriate and then build the desired image as normal. |
128 | </tip> | 128 | </tip> |
129 | </chapter> | 129 | </chapter> |
130 | <!-- | 130 | <!-- |
131 | vim: expandtab tw=80 ts=4 | 131 | vim: expandtab tw=80 ts=4 |
132 | --> | 132 | --> |