@drebelpai the reason is that 6.5 will only enter the LTS phase after 6.5.3 is
out.

That is, for the first patch level releases, any LTS release is just a normal release, with both open source and commercial sources being available. But after Qt 6.6.0 is released, Qt 6.5 normally wouldn't get any scheduled updates anymore. This is where the commercial-only LTS releases come into play.

You also notice that in the screenshot: There's a lts-6.2.5 branch, but no lts-6.2.4 branch. This is because Qt 6.2.4 was still a non-lts patch level release (see also https://wiki.qt.io/Qt_6.2_Release).

Anyhow, I agree that the terminology here is confusing.

@jsulm I wasn't aware it was not released yet. Back to building Yocto for Qt 5.15.2 then. Thanks!

Sorry folks, the question was vague and the begining of a development...
Apparently to make Qt Quick Scene Graph work on an embedded system displaying GUI on the frame buffer, we need to recompile Qt on Yocto, and provide fake/dummy libraries ligEGL.so and libGLES.so
Obviously it will be rendered using software, as there is no hardware graphic support in that case, but it still needs "empty" libGLES.so to do so.
...

Sorry to reopen the ticket. But I think we can add an answer for whoever ends up here in the future.

I have the same issue, also had libxkbcommon into the image under /usr/lib/ and kept having the same error.

The problem was basically on Yocto build I missed configuring the qtbase PACKAGECONFIG variable to enable the xkbcommon option.

To do that, you add a new layer, create a qtbase_%.bbappend file and add:

PACKAGECONFIG:append:<machinename> = " xkbcommon"

NOTE: If you don't add the <machinename> you will have failures because other packages won't have the -native extension.
NOTE2: make sure to do that in a clean build (or clean all qt packages), other ptest will fail complaining that a configuration was changed and it doesn't know why.

Hi,

Well, if your target sysroot does not provide X11, then the xcb backend won't work. Either add X11 to your target or select a more appropriate backend like EGLFS, LinuxFB, wayland, etc.

@SGaist I don't think so but in the meantime I don't see any package which could do it. My board support OpenGl ES2 so I tried some stuff like adding "PACKAGE CONFIG += "gles2" " to my qtbase bb file but nothing has changed ...

Also tried to add PACKAGECONFIG_append_pn-qtbase = "gles2" in my local.conf but no change.

After some googling, I found that the error was printed by this code : https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/platforms/xcb/qxcbbackingstore.cpp?h=dev (line 371)

Edit: Closing this issue, it was a problem of platform (by default it was using x11 which is not the one used by my embedded device) . Thanks a lot for your help again !

This is the output when I build from command line with qmake/make :

root@debian:~# echo $QMAKESPEC root@debian:~# source /opt/qtsdk-Guinault-2020.03/environment-setup-armv7at2hf-neon-linux-gnueabi root@debian:~# echo $QMAKESPEC /opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi/usr/lib/mkspecs/linux-oe-g++ root@debian:~# mkdir hellowolrd_qt root@debian:~# cd hellowolrd_qt/ root@debian:~/hellowolrd_qt# nano helloworld.cpp root@debian:~/hellowolrd_qt# nano helloworld.pro root@debian:~/hellowolrd_qt# qmake helloworld.pro Info: creating stash file /root/hellowolrd_qt/.qmake.stash root@debian:~/hellowolrd_qt# make arm-linux-gnueabihf-g++ -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard --sysroot=/opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi -c -pipe -isystem/home/guinault/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/arm-linux-gnueabihf/include -O2 -pipe -g -feliminate-unused-debug-types --sysroot=/opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi -O2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -I/opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi/usr/include/QtWidgets -I/opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi/usr/include/QtGui -I/opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi/usr/include/QtCore -I. -I/opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi/usr/lib/mkspecs/linux-oe-g++ -o helloworld.o helloworld.cpp In file included from /opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi/usr/include/QtGui/qtguiglobal.h:43, from /opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi/usr/include/QtWidgets/qtwidgetsglobal.h:43, from /opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi/usr/include/QtWidgets/qapplication.h:43, from /opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi/usr/include/QtWidgets/QApplication:1, from helloworld.cpp:1: /opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi/usr/include/QtCore/qglobal.h:45:12: fatal error: type_traits: No such file or directory # include <type_traits> ^~~~~~~~~~~~~ compilation terminated. Makefile:547: recipe for target 'helloworld.o' failed make: *** [helloworld.o] Error 1 root@debian:~/hellowolrd_qt#

And this is CXX and CXXFLAGS :

root@debian:~/hellowolrd_qt# . /opt/qtsdk-Guinault-2020.03/environment-setup-armv7at2hf-neon-linux-gnueabi root@debian:~/hellowolrd_qt# echo $CXX arm-linux-gnueabihf-g++ -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard --sysroot=/opt/qtsdk-Guinault-2020.03/sysroots/armv7at2hf-neon-linux-gnueabi root@debian:~/hellowolrd_qt# echo $CXXFLAGS -isystem/home/guinault/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/arm-linux-gnueabihf/include -O2 -pipe -g -feliminate-unused-debug-types

Anyone can help me please ?

Thank you

Sébastien

@nikoPol said in Programme QT ne reconnait les drivers MYSQL:

Il n'y a pas d'autre moyen

Non, il faut compiler les drivers pour votre cible avec les paramètres adéquats, soit directement à partir de Yocto, soit "à la main", à partir des sources de Qt.

Peut-être que ce lien pourra vous être utile: https://www.udoo.org/forum/threads/solved-how-to-use-sql-model-with-qt5-layer.5136/

Désolé, je n'ai que des connaissances de base concernant Yocto... Et ca fait bien 3 ans que je ne l'ai plus mis en oeuvre!

Just wanted to say thanks! I ran into the same issue (building qtwebengine) on Ubuntu 18.04 host and this fixed it.

I'm adding it to my personal list of prerequisites for my Boot2Qt Yocto builds....

@Cleiton-Bueno Thank you very much for providing me more information on the Yocto language selection.

I've got the same situation on my iMX6 with Yocto Rocko. Any solution for this issue? Is the same situation on new release Sumo or Thud?