How to create your own image

Stable: 13.05.2022 - 13:17 / Revision: 04.04.2022 - 07:21

I am here to prevent the first-page-empty bug!

Template:ArticleMainWriter Template:ArticleApprovedVersion


1 Article purpose

The main goal of this article is to describe how to customize images to fit application requirements.
The idea is to add missing tools in the user file system.
Tools are related to kernel, network, audio, ui, ...

2 Prerequisites

The OpenSTLinux distribution delivery must be already installed.

3 Available ST images

3.1 OpenEmbedded images

The OpenEmbedded build system provides severals example images to satisfy different needs.
All details are explained Yocto Megamanual Reference Images
Some existing images are located here: <path of OpenSTLinux distribution delivery>/openembedded-core/meta/recipes-*/images/*.bb

The core-image-base can be a good starting points and a source or inspiration for creating user's own images:

openembedded-core            
├── meta  
│   ├── classes
│       ├── Template:Highlight2
│   ├── recipes-core
│       ├── images
│           ├── Template:Highlight2
└── [...]


In addition OpenSTLinux Distribution provides even more images, still derived from OpenEmbedded, and that can be used as example and for demonstration.

Warning white.png Warning
ST images are not optimized in term of size or features.

3.2 Official OpenSTLinux images

  • st-image-weston : OpenSTLinux weston image with basic Wayland support (if enable in distro)

This image is located here : <path of OpenSTLinux distribution delivery>/meta-st/meta-st-openstlinux/recipes-st/images/st-image-weston.bb

3.3 Others OpenSTLinux images

3.3.1 Supported images

  • st-image-core  : OpenSTLinux core image

This image is located here : <path of OpenSTLinux distribution delivery>/meta-st/meta-st-openstlinux/recipes-st/images/st-image-core.bb

meta-st-openstlinux            
├── recipes-st  
│   ├── images
│       ├── Template:Highlight2
│       ├── st-image.inc
│       ├── Template:Highlight2
│   ├── packagegroups
│       ├── Template:Highlight2
└── [...]

3.3.2 Images proposed as example-only

  • st-example-image-qt : ST example of image based on QT framework (require 'openstlinux-eglfs' distro)
  • st-example-image-x11 : ST example of image based on X11 (require 'openstlinux-x11' distro)
  • st-example-image-xfce : ST example of image based on XFCE framework (require 'openstlinux-x11' distro)

More images are available here : <path of OpenSTLinux distribution delivery>/meta-st/meta-st-openstlinux/recipes-samples/images/

meta-st-openstlinux            
├── recipes-samples  
│   ├── images
│       ├── Template:Highlight2
│       ├── Template:Highlight2
│       ├── Template:Highlight2
│       │ [...]
└── [...]

4 Customizing images

Several ways are explained and described here Yocto Megamanual Customizing Images

The way recommended and used by ST is to follow the method described in chapters Customizing Images Using Custom .bb Files and Customizing Images Using Custom Package Groups of Yocto Megamanual.

IMPORTANT NOTICE – READ CAREFULLY
STMicroelectronics NV and its subsidiaries ("ST") reserve the right to make changes, corrections, enhancements, modifications, and improvements to ST products and/or to this document at any time without notice. Purchasers should obtain the latest relevant information on ST products before placing orders. ST products are sold pursuant to ST’s terms and conditions of sale in place at the time of order acknowledgment.

Purchasers are solely responsible for the choice, selection, and use of ST products and ST assumes no liability for application assistance or the design of purchasers’ products.

No license, express or implied, to any intellectual property right is granted by ST herein.

Resale of ST products with provisions different from the information set forth herein shall void any warranty granted by ST for such product.

ST and the ST logo are trademarks of ST. For additional information about ST trademarks, refer to www.st.com/trademarks. All other product or service names are the property of their respective owners.

Information in this document supersedes and replaces information previously supplied in any prior versions of this document.