ref-images.rst 6.3 KB

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