diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-03-28 06:51:59 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-04-04 14:13:36 +0100 |
commit | d4366144248ffa9ee50d717143b1e87a8a3aa437 (patch) | |
tree | 1f234f81d5c5641dc97b328a0732a530e586fcd7 /documentation/ref-manual/ref-images.xml | |
parent | a8532b0f84f957df679c7923c337f09a418b6263 (diff) | |
download | openembedded-core-contrib-d4366144248ffa9ee50d717143b1e87a8a3aa437.tar.gz |
ref-manual: Updates to the "Images" chapter.
Made sure the list of shipped (supported) images was up-to-date.
Had to add a couple. Also, some extra edits to support the
new list.
(From yocto-docs rev: db5bc1dd0079d0d8db67653a9878205d4b89258f)
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/ref-images.xml')
-rw-r--r-- | documentation/ref-manual/ref-images.xml | 75 |
1 files changed, 46 insertions, 29 deletions
diff --git a/documentation/ref-manual/ref-images.xml b/documentation/ref-manual/ref-images.xml index 0a827ca235..e08fd19adf 100644 --- a/documentation/ref-manual/ref-images.xml +++ b/documentation/ref-manual/ref-images.xml @@ -31,13 +31,25 @@ </literallayout> These recipes reside in the <filename>meta/recipes-core/images</filename>, <filename>meta/recipes-extended/images</filename>, - <filename>meta/recipes-graphics/images</filename>, and - <filename>meta/recipes-sato/images</filename> directories - within the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. + <filename>meta/recipes-graphics/images</filename>, + <filename>meta/recipes-qt/images</filename>, + <filename>meta/recipes-rt/images</filename>, + <filename>meta/recipes-sato/images</filename>, and + <filename>meta-skeleton/recipes-multilib/images</filename> directories + within the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. Although the recipe names are somewhat explanatory, here is a list that describes them: </para> <itemizedlist> + <listitem><para><emphasis><filename>build-appliance-image</filename>:</emphasis> + An example virtual machine that contains all the pieces required to + run builds using the build system as well as the build system itself. + You can boot and run the image using either the + <ulink url='http://www.vmware.com/products/player/overview.html'>VMware Player</ulink> + or <ulink url='http://www.vmware.com/products/workstation/overview.html'>VMware Workstation</ulink>. + For more information on this image, see the + <ulink url='&YOCTO_HOME_URL;/documentation/build-appliance'>Build Appliance</ulink> page on + the Yocto Project website.</para></listitem> <listitem><para><emphasis><filename>core-image-base</filename>:</emphasis> A console-only image that fully supports the target device hardware.</para></listitem> <listitem><para><emphasis><filename>core-image-minimal</filename>:</emphasis> @@ -58,14 +70,12 @@ for the Minimal MTD Utilities, which let the user interact with the MTD subsystem in the kernel to perform operations on flash devices. </para></listitem> - <listitem><para><emphasis><filename>core-image-x11</filename>:</emphasis> - A very basic X11 image with a terminal. - </para></listitem> <listitem><para><emphasis><filename>core-image-basic</filename>:</emphasis> A console-only image with more full-featured Linux system functionality installed.</para></listitem> <listitem><para><emphasis><filename>core-image-lsb</filename>:</emphasis> - An image that conforms to the Linux Standard Base (LSB) specification.</para></listitem> + An image that conforms to the Linux Standard Base (LSB) specification. + </para></listitem> <listitem><para><emphasis><filename>core-image-lsb-dev</filename>:</emphasis> A <filename>core-image-lsb</filename> image that is suitable for development work using the host. @@ -79,41 +89,48 @@ <listitem><para><emphasis><filename>core-image-clutter</filename>:</emphasis> An image with support for the Open GL-based toolkit Clutter, which enables development of rich and animated graphical user interfaces.</para></listitem> + <listitem><para><emphasis><filename>core-image-gtk-directfb</filename>:</emphasis> + An image that uses <filename>gtk+</filename> over <filename>directfb</filename> + instead of X11. + In order to build, this image requires specific distro configuration that enables + <filename>gtk</filename> over <filename>directfb</filename>.</para></listitem> + <listitem><para><emphasis><filename>core-image-x11</filename>:</emphasis> + A very basic X11 image with a terminal. + </para></listitem> + <listitem><para><emphasis><filename>qt4e-demo-image</filename>:</emphasis> + An image that launches into the demo application for the embedded + (not based on X11) version of Qt.</para></listitem> + <listitem><para><emphasis><filename>core-image-rt</filename>:</emphasis> + A <filename>core-image-minimal</filename> image plus a real-time test suite and + tools appropriate for real-time use.</para></listitem> + <listitem><para><emphasis><filename>core-image-rt-sdk</filename>:</emphasis> + A <filename>core-image-rt</filename> image that includes everything in + <filename>meta-toolchain</filename>. + The image also includes development headers and libraries to form a complete + stand-alone SDK and is suitable for development using the target. + </para></listitem> <listitem><para><emphasis><filename>core-image-sato</filename>:</emphasis> An image with Sato support, a mobile environment and visual style that works well with mobile devices. The image supports X11 with a Sato theme and applications such as - a terminal, editor, file manager, media player, and so forth.</para></listitem> + a terminal, editor, file manager, media player, and so forth. + </para></listitem> <listitem><para><emphasis><filename>core-image-sato-dev</filename>:</emphasis> A <filename>core-image-sato</filename> image suitable for development using the host. The image includes libraries needed to build applications on the device itself, testing and profiling tools, and debug symbols. - This image was formerly <filename>core-image-sdk</filename>.</para></listitem> + This image was formerly <filename>core-image-sdk</filename>. + </para></listitem> <listitem><para><emphasis><filename>core-image-sato-sdk</filename>:</emphasis> A <filename>core-image-sato</filename> image that includes everything in meta-toolchain. The image also includes development headers and libraries to form a complete standalone SDK and is suitable for development using the target.</para></listitem> - <listitem><para><emphasis><filename>core-image-rt</filename>:</emphasis> - A <filename>core-image-minimal</filename> image plus a real-time test suite and - tools appropriate for real-time use.</para></listitem> - <listitem><para><emphasis><filename>core-image-rt-sdk</filename>:</emphasis> - A <filename>core-image-rt</filename> image that includes everything in - <filename>meta-toolchain</filename>. - The image also includes development headers and libraries to form a complete - stand-alone SDK and is suitable for development using the target.</para></listitem> - <listitem><para><emphasis><filename>core-image-gtk-directfb</filename>:</emphasis> - An image that uses <filename>gtk+</filename> over <filename>directfb</filename> - instead of X11. - In order to build, this image requires specific distro configuration that enables - <filename>gtk</filename> over <filename>directfb</filename>.</para></listitem> - <listitem><para><emphasis><filename>build-appliance-image</filename>:</emphasis> - An image you can boot and run using either the - <ulink url='http://www.vmware.com/products/player/overview.html'>VMware Player</ulink> - or <ulink url='http://www.vmware.com/products/workstation/overview.html'>VMware Workstation</ulink>. - For more information on this image, see the - <ulink url='&YOCTO_HOME_URL;/documentation/build-appliance'>Build Appliance</ulink> page on - the Yocto Project website.</para></listitem> + <listitem><para><emphasis><filename>core-image-multilib-example</filename>:</emphasis> + An example image that includes a <filename>lib32</filename> version + of Bash into an otherwise standard <filename>sato</filename> image. + The image assumes a "lib32" multilib has been enabled in the your + configuration.</para></listitem> </itemizedlist> <tip> |