Add Wayland submodule on Raspberry Pi

[Hardy]

Hello,

i build Qt6.2.4 on a Raspi 4 with bullseye lite following this tutorial https://www.tal.org/tutorials/building-qt-62-raspberry-pi-raspberry-pi-os
After a few hours it works, means, a hello world code leads in an executable using cmake. BUT, it is useless bcs a proper windowmanager is missing. With X11 (installed by hand) i can see the hello world, but thats it, any other interaction is not possible.
Other installed platform plugins are not working (nothing happens, black screen or an error appears). So i want to add wayland submodul to the installation, but when i configure it, in the summary i see "Raspberry Pi ... no". I guess it is pointless to compile it bcs it will not work!?
Does somebody have an idea/howto to get an "Raspberry Pi .... yes" when configuring wayland submodul?

Goal ofc: Get Qt Apps working on the pi. May be there is a propper approach than using wayland i haven't seen yet!?

Thanks in advance!

Greetings,
Hardy

[Ronel_qtmaster]

@Hardy Why not using Yocto for exemple?it supports Qt as well

[The Qt Mayssa]

@Hardy said in Add Wayland submodule on Raspberry Pi:

be there is a propper app

I guess when compiling the qt creator you can change the properties . Like what's have been done in the section "Configure the Qt 6.2 build" to enable openssl ...

[Ronel_qtmaster]

@The-Qt-Mayssa it is the same with yocto.
Now about your problem, when you want to crosscompile qt for raspberry, to have all the platforms working, you should have the required plugins for each platform installed and been found by the script.Therefore you need to synchronize your sysroot with rpi one.

Moreover, i have noticed that while compiling qt for raspberry pi, the script has a fixed name of the lib required to build a plugin platform.Therefore the name of the libs in the sysroot must correspond to what the script is searching for a plugin platform.That is the case for EGLFS PLUGIN.

On the other hand Yocto is pretty simple and your image does not depends on Raspbian

[Hardy]

@Ronel_qtmaster Thanks for the replys.
Honestly i don't want to start from scratch with a new linux only bcs of a missing windowmanager. Further i don't want have the overhead of full raspbian installation, the reason why i always choose lite. But now i need the first time a small GUI. I played around with pysimplegui. It is nice but does not fit my needs. I have not much experience with python but 15 years experience with qt.. in programming not installing/configuring.
I build qt directly on the pi, the reason why this took several hours. Another reason why i don't want to kick this time in the dustbin...
I read that qt modul wayland has dependencies e.g. to https://wayland.freedesktop.org/building.html
But i'm not shure whether this is the reason for configure output "Raspberry Pi ... no".!? Can i see somewhere the condition which decides about yes or no to see what exactly is missing?

To be honest, i would have expected that a module is collecting and installing everything needed for the specific machine (here: raspi4/bullseye). Obviously a wrong assumption :-(
But at least i need to know what i have to install to satisfy qtwayland submodul.

PS I don't use QtCreator. I use CLion with a remote CMake toolchain, so that the code, written on my Win11 laptop gets build on the target/raspi. That works fine.

[Ronel_qtmaster]

@Hardy check this https://bugfreeblog.duckdns.org/2013/03/bring-up-qt-501-on-raspberry-pi-with.html

[Hardy]

@Ronel_qtmaster Thanks for the hint.
Unfortunately it seems not be suitable for Qt6 on bullseye. The tutorial is for qt5 an weezy.
First obstacle is sudo apt-get install libgstreamer0.10-dev libgstreamer-plugins-base0.10-dev libgstreamer-plugins-bad0.10-dev, i solved it by replacing 0.10 with 1.0, that works.
But dead end is here:
pi@papaBjarne:~/dev/tools/qt $ git clone git://anongit.freedesktop.org/wayland/waylan
Klone nach 'waylan' ...
fatal: Fehler am anderen Ende: access denied or repository not exported: /wayland/waylan

Knowing that it would fail I started the build of qt wayland, it crashed... something with scanner....

I gave up, it just takes too much time!
I installed bookworm with the huge overhead of the desktop.
However, my dummy qt6 application, remote build via CLion runs without any problems, a MainWindow and a button....

Even 15 years ago it was a drama to get Qt running on small embedded systems. It's a pity that nothing seems to have changed to this day!

But thanks for your approach to help, i appreciate it!

[Ronel_qtmaster]

@Hardy okay you are welcome.many things have changed though.You can still build your qt image with yocto.Also, note that wayland is not really recommended for embedded systems