images.rst 6.1 KB

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