diff options
Diffstat (limited to 'documentation/ref-manual/ref-images.rst')
-rw-r--r-- | documentation/ref-manual/ref-images.rst | 137 |
1 files changed, 137 insertions, 0 deletions
diff --git a/documentation/ref-manual/ref-images.rst b/documentation/ref-manual/ref-images.rst new file mode 100644 index 0000000000..62863b640a --- /dev/null +++ b/documentation/ref-manual/ref-images.rst | |||
@@ -0,0 +1,137 @@ | |||
1 | ****** | ||
2 | Images | ||
3 | ****** | ||
4 | |||
5 | The OpenEmbedded build system provides several example images to satisfy | ||
6 | different needs. When you issue the ``bitbake`` command you provide a | ||
7 | “top-level” recipe that essentially begins the build for the type of | ||
8 | image you want. | ||
9 | |||
10 | .. note:: | ||
11 | |||
12 | Building an image without GNU General Public License Version 3 | ||
13 | (GPLv3), GNU Lesser General Public License Version 3 (LGPLv3), and | ||
14 | the GNU Affero General Public License Version 3 (AGPL-3.0) components | ||
15 | is only supported for minimal and base images. Furthermore, if you | ||
16 | are going to build an image using non-GPLv3 and similarly licensed | ||
17 | components, you must make the following changes in the | ||
18 | local.conf | ||
19 | file before using the BitBake command to build the minimal or base | ||
20 | image: | ||
21 | :: | ||
22 | |||
23 | 1. Comment out the EXTRA_IMAGE_FEATURES line | ||
24 | 2. Set INCOMPATIBLE_LICENSE = "GPL-3.0 LGPL-3.0 AGPL-3.0" | ||
25 | |||
26 | |||
27 | From within the ``poky`` Git repository, you can use the following | ||
28 | command to display the list of directories within the `Source | ||
29 | Directory <#source-directory>`__ that contain image recipe files: $ ls | ||
30 | meta*/recipes*/images/*.bb | ||
31 | |||
32 | Following is a list of supported recipes: | ||
33 | |||
34 | - ``build-appliance-image``: An example virtual machine that contains | ||
35 | all the pieces required to run builds using the build system as well | ||
36 | as the build system itself. You can boot and run the image using | ||
37 | either the `VMware | ||
38 | Player <http://www.vmware.com/products/player/overview.html>`__ or | ||
39 | `VMware | ||
40 | Workstation <http://www.vmware.com/products/workstation/overview.html>`__. | ||
41 | For more information on this image, see the `Build | ||
42 | Appliance <&YOCTO_HOME_URL;/software-item/build-appliance/>`__ page | ||
43 | on the Yocto Project website. | ||
44 | |||
45 | - ``core-image-base``: A console-only image that fully supports the | ||
46 | target device hardware. | ||
47 | |||
48 | - ``core-image-clutter``: An image with support for the Open GL-based | ||
49 | toolkit Clutter, which enables development of rich and animated | ||
50 | graphical user interfaces. | ||
51 | |||
52 | - ``core-image-full-cmdline``: A console-only image with more | ||
53 | full-featured Linux system functionality installed. | ||
54 | |||
55 | - ``core-image-lsb``: An image that conforms to the Linux Standard Base | ||
56 | (LSB) specification. This image requires a distribution configuration | ||
57 | that enables LSB compliance (e.g. ``poky-lsb``). If you build | ||
58 | ``core-image-lsb`` without that configuration, the image will not be | ||
59 | LSB-compliant. | ||
60 | |||
61 | - ``core-image-lsb-dev``: A ``core-image-lsb`` image that is suitable | ||
62 | for development work using the host. The image includes headers and | ||
63 | libraries you can use in a host development environment. This image | ||
64 | requires a distribution configuration that enables LSB compliance | ||
65 | (e.g. ``poky-lsb``). If you build ``core-image-lsb-dev`` without that | ||
66 | configuration, the image will not be LSB-compliant. | ||
67 | |||
68 | - ``core-image-lsb-sdk``: A ``core-image-lsb`` that includes everything | ||
69 | in the cross-toolchain but also includes development headers and | ||
70 | libraries to form a complete standalone SDK. This image requires a | ||
71 | distribution configuration that enables LSB compliance (e.g. | ||
72 | ``poky-lsb``). If you build ``core-image-lsb-sdk`` without that | ||
73 | configuration, the image will not be LSB-compliant. This image is | ||
74 | suitable for development using the target. | ||
75 | |||
76 | - ``core-image-minimal``: A small image just capable of allowing a | ||
77 | device to boot. | ||
78 | |||
79 | - ``core-image-minimal-dev``: A ``core-image-minimal`` image suitable | ||
80 | for development work using the host. The image includes headers and | ||
81 | libraries you can use in a host development environment. | ||
82 | |||
83 | - ``core-image-minimal-initramfs``: A ``core-image-minimal`` image that | ||
84 | has the Minimal RAM-based Initial Root Filesystem (initramfs) as part | ||
85 | of the kernel, which allows the system to find the first “init” | ||
86 | program more efficiently. See the | ||
87 | ```PACKAGE_INSTALL`` <#var-PACKAGE_INSTALL>`__ variable for | ||
88 | additional information helpful when working with initramfs images. | ||
89 | |||
90 | - ``core-image-minimal-mtdutils``: A ``core-image-minimal`` image that | ||
91 | has support for the Minimal MTD Utilities, which let the user | ||
92 | interact with the MTD subsystem in the kernel to perform operations | ||
93 | on flash devices. | ||
94 | |||
95 | - ``core-image-rt``: A ``core-image-minimal`` image plus a real-time | ||
96 | test suite and tools appropriate for real-time use. | ||
97 | |||
98 | - ``core-image-rt-sdk``: A ``core-image-rt`` image that includes | ||
99 | everything in the cross-toolchain. The image also includes | ||
100 | development headers and libraries to form a complete stand-alone SDK | ||
101 | and is suitable for development using the target. | ||
102 | |||
103 | - ``core-image-sato``: An image with Sato support, a mobile environment | ||
104 | and visual style that works well with mobile devices. The image | ||
105 | supports X11 with a Sato theme and applications such as a terminal, | ||
106 | editor, file manager, media player, and so forth. | ||
107 | |||
108 | - ``core-image-sato-dev``: A ``core-image-sato`` image suitable for | ||
109 | development using the host. The image includes libraries needed to | ||
110 | build applications on the device itself, testing and profiling tools, | ||
111 | and debug symbols. This image was formerly ``core-image-sdk``. | ||
112 | |||
113 | - ``core-image-sato-sdk``: A ``core-image-sato`` image that includes | ||
114 | everything in the cross-toolchain. The image also includes | ||
115 | development headers and libraries to form a complete standalone SDK | ||
116 | and is suitable for development using the target. | ||
117 | |||
118 | - ``core-image-testmaster``: A "master" image designed to be used for | ||
119 | automated runtime testing. Provides a "known good" image that is | ||
120 | deployed to a separate partition so that you can boot into it and use | ||
121 | it to deploy a second image to be tested. You can find more | ||
122 | information about runtime testing in the "`Performing Automated | ||
123 | Runtime | ||
124 | Testing <&YOCTO_DOCS_DEV_URL;#performing-automated-runtime-testing>`__" | ||
125 | section in the Yocto Project Development Tasks Manual. | ||
126 | |||
127 | - ``core-image-testmaster-initramfs``: A RAM-based Initial Root | ||
128 | Filesystem (initramfs) image tailored for use with the | ||
129 | ``core-image-testmaster`` image. | ||
130 | |||
131 | - ``core-image-weston``: A very basic Wayland image with a terminal. | ||
132 | This image provides the Wayland protocol libraries and the reference | ||
133 | Weston compositor. For more information, see the "`Using Wayland and | ||
134 | Weston <&YOCTO_DOCS_DEV_URL;#dev-using-wayland-and-weston>`__" | ||
135 | section in the Yocto Project Development Tasks Manual. | ||
136 | |||
137 | - ``core-image-x11``: A very basic X11 image with a terminal. | ||