Skip to main content
Associate
January 27, 2026
Solved

X-LINUX-QT Starter Package Generation

  • January 27, 2026
  • 3 replies
  • 168 views

On the X-LINUX-QT Starter Package Wiki page it states "The X-LINUX-QT expansion package compatible with ecosystem release v6.1.0 provides only the Distribution package, which can be used to generate the Starter and Developer packages".

Has anyone generated the QT starter package in v6.1.0?

The image produced by "bitbake st-image-qt package-index" launches with the GTK starter package, not the QT starter package.

Best answer by furky

Two modifications are required to generate X-LINUX-QT Starter Package from the distribution.

Append

IMAGE_INSTALL:append = " stlauncher"

to the local.conf file located inside the build directory/conf.

 

Then modify the meta-st/meta-st-x-linux-qt/recipes-st-launcher/stlauncher/files/start_up_stlauncher.sh file to force QT_QPA_PLATFORM=wayland. By the default QT_QPA_PLATFORM is set in the environment variables as QT_QPA_PLATFORM=linuxfb.

3 replies

jumman_JHINGA
Senior III
January 28, 2026

I’ve tried generating the Qt Starter package on v6.1.0 starting from the Distribution package, as mentioned in the wiki.

In practice, the process is very time-consuming, and in my case the build consistently fails around 75–80% completion with missing file / dependency errors during the BitBake process. I haven’t been able to complete a clean build yet

furkyAuthorBest answer
Associate
January 28, 2026

Two modifications are required to generate X-LINUX-QT Starter Package from the distribution.

Append

IMAGE_INSTALL:append = " stlauncher"

to the local.conf file located inside the build directory/conf.

 

Then modify the meta-st/meta-st-x-linux-qt/recipes-st-launcher/stlauncher/files/start_up_stlauncher.sh file to force QT_QPA_PLATFORM=wayland. By the default QT_QPA_PLATFORM is set in the environment variables as QT_QPA_PLATFORM=linuxfb.

furkyAuthor
Associate
January 30, 2026

A simpler solution is to ensure the machine variable is the exact board that you have, not the generic stm32mp1 or stm32mp2 values.

 

e.g. For the stm32mp257f-DK board:

DISTRO=openstlinux-weston MACHINE=stm32mp25-disco source layers/meta-st/scripts/envsetup.sh