I'm constantly trying to solve the issue... any help would be much appreciated.. I have noticed that when I choose different qmake, MySQL plugin is configured and prepared for building. Please have a look: embsys@JT-UBUNTU:~/raspi/test$ /home/embsys/Qt5.14.2/5.14.2/gcc_64/bin/qmake /home/embsys/raspi/qt-everywhere-src-5.12.3/qtbase/src/plugins/sqldrivers/sqldrivers.pro -- MYSQL_PREFIX=/home/embsys/raspi/sysroot/usr/lib/arm-linux-gnueabihf Running configuration tests... Checking for DB2 (IBM)... no Checking for InterBase... no Checking for MySQL... yes Checking for OCI (Oracle)... no Checking for ODBC... no Checking for PostgreSQL... yes Checking for SQLite (version 2)... no Checking for TDS (Sybase)... no Done running configuration tests. Configure summary: Qt Sql Drivers: DB2 (IBM) .............................. no InterBase .............................. no MySql .................................. yes OCI (Oracle) ........................... no ODBC ................................... no PostgreSQL ............................. yes SQLite2 ................................ no SQLite ................................. yes Using system provided SQLite ......... no TDS (Sybase) ........................... no Qt is now configured for building. Just run 'make'. Once everything is built, you must run 'make install'. Qt will be installed into '/home/embsys/Qt5.14.2/5.14.2/gcc_64'. Prior to reconfiguration, make sure you remove any leftovers from the previous build. Unfortunately when I try to use the qmake for cross-compiler path I get the following: embsys@JT-UBUNTU:~/raspi/test$ /home/embsys/raspi/qtbase/qmake/qmake /home/embsys/raspi/qt-everywhere-src-5.12.3/qtbase/src/plugins/sqldrivers/sqldrivers.pro -- MYSQL_PREFIX=/home/embsys/raspi/sysroot/usr/lib/arm-linux-gnueabihf Running configuration tests... Checking for DB2 (IBM)... no Checking for InterBase... no Checking for MySQL... no Checking for OCI (Oracle)... no Checking for ODBC... yes Checking for PostgreSQL... yes Checking for SQLite (version 2)... yes Checking for TDS (Sybase)... yes Done running configuration tests. Configure summary: Qt Sql Drivers: DB2 (IBM) .............................. no InterBase .............................. no MySql .................................. no OCI (Oracle) ........................... no ODBC ................................... yes PostgreSQL ............................. yes SQLite2 ................................ yes SQLite ................................. yes Using system provided SQLite ......... no TDS (Sybase) ........................... yes Qt is now configured for building. Just run 'make'. Once everything is built, you must run 'make install'. Qt will be installed into '/home/embsys/raspi/qt5pi'. Prior to reconfiguration, make sure you remove any leftovers from the previous build. I lack good knowledge about qmake tool, but maybe there is something wrong with the qmake I try to use for Raspberry PI. BTW I have different qmakes in my host: embsys@JT-UBUNTU:~/raspi$ sudo find / -name qmake -type f /home/embsys/ti-processor-sdk-linux-rt-am335x-evm-05.03.00.07/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/qt5/qmake /home/embsys/ti-processor-sdk-linux-rt-am335x-evm-05.02.00.10/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/qt5/qmake /home/embsys/ti-processor-sdk-linux-am335x-evm-05.02.00.10/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/qt5/qmake /home/embsys/Qt5.14.2/qt-everywhere-src-5.14.2/qtbase/bin/qmake /home/embsys/Qt5.14.2/5.14.2/gcc_64/bin/qmake /home/embsys/raspi/qt5/bin/qmake /home/embsys/raspi/qtbase/bin/qmake /home/embsys/raspi/qtbase/qmake/qmake find: ‘/run/user/1000/doc’: Permission denied find: ‘/run/user/1000/gvfs’: Permission denied /usr/lib/x86_64-linux-gnu/qt4/bin/qmake /usr/lib/qt5/bin/qmake Could sb explain what is the difference between those qmakes that are in RPi paths? namely: /home/embsys/raspi/qt5/bin/qmake /home/embsys/raspi/qtbase/bin/qmake /home/embsys/raspi/qtbase/qmake/qmake I tried all of them but they give the same results. Is it possible that I somehow have a problem with Qt instalation for cross-compiling (and consequently with qmake) and this is the problem?

@vishbynature It's config.log file located in the same directory from which you called configure. It is a text file, nothing special. Look for compile errors in that file related to to what you need.

@SGaist yes. at that time i did not know about Qtconnectivity module.

@Pablo-J-Rogina I will look into it.

Seems to be a bug reported here QTBUG-50244 Nobody tried to integrate MySQL for a Raspberry Pi project already ?! no workaround?! Seems strange :(

@sneubert Thanks :)

@Andrex_Qt said in Responsive QtMainWindow on Startup.: i access them through C Api Could it be possible you share a link to such API for the benefit of other users just in case?

Hi, I described the steps I followed in a post over here, https://mechatronicsblog.com/cross-compile-and-deploy-qt-5-12-for-raspberry-pi/ Some people found some issues and posted comments there, the “qendian” issue seems to be related to this bug, there is also a patch there. https://bugreports.qt.io/browse/QTBUG-71945

May I suggest to change for Python 3 ? Python 2.7 will reached end of life next year so it's not a good idea to start a new project with it.

I tested it with Qt 5.11.0, but more deficiency detected. The General Attribute also undetected and characteristic write is not working :(

No, because they were neved emitted. I just found this: https://bugreports.qt.io/browse/QTBUG-38401, it seems that they are not implemented yet for Bluez 5. However, I would like to set the pin in only one-way, the raspberry shouldn't accept any pairing if the pin code (probably hardcoded in the raspberry) is different from the one entered by the user. Anyway, I'm not sure if this is possible.

I have found a solution here. Looks like Ubuntu couldn't run 32bit binary, but it's working now.

@ronpetit said in Qt on Raspberry pi3: @sierdzio I'm running it without X server, as I should Now, I'm curious about this, what libs are you using for glesv2 and egl?, I'm using the ones in /opt/vc/lib folder, and I also cross compiled the Qt with those Oh I don't remember to be honest. I think I didn't change anything from stock settings. I also didn't specify the OpenGL libs manually anywhere when building Qt or apps.

@Worly said in Qt cross platform compilation with QtRpi to rpi3 - could not find "eglfs": QtRpi has only up to 5.7.0 version of Qt, does that mean that I have to use v5.7.0 plugins or I can use the latest? Would you consider going through the steps from this guide? It allows you to cross compile Qt for RPi and it's been used with newer Qt versions and several RPi models.

@SGaist I found the solution in the mplayer's docs, the -wid not working in linuxfb environment. The qprocess started the mplayer who writes the framebuffer directly, it's working.

@Jerwinprabu Thank You. It is working fine now.

Not sure, but it sounds like a broken toolchain. Make sure your cross compilation toolchain and sysroot are valid.

@Xenoshell If a command/tool needs root rights it is better to set http://linuxg.net/how-to-set-the-setuid-and-setgid-bit-for-files-in-linux-and-unix/ instead of running whole IDE as root! I never saw a need to run an IDE as root and I'm software developer for quite some time.

Ok, I've missed that article. From the looks of it, you seem to be currently essentially interested in building qtbase, so you could call configure directly in it to shorten the list of options. Intuitively, I'd avoid the reduce-exports and sysroot parameters.

Thank you a lot , i will looking for it.

@moldovan.catalin You can create symbolic link in /opt/vc/lib pointing to these libraries but having old names.

thanks a lot for help i already solved it. I just deleted the old compiler added new set same path and restart QT finally it works :)

Just for the sake of completeness, this simple patch enables building qt5script v5.12.7 on Raspberry Pi 3: diff –git a/src/3rdparty/javascriptcore/JavaScriptCore/wtf/Platform.h b/src/3rdparty/javascriptcore/JavaScriptCore/wtf/Platform.h index a4695a2..897c90c 100644 — a/src/3rdparty/javascriptcore/JavaScriptCore/wtf/Platform.h +++ b/src/3rdparty/javascriptcore/JavaScriptCore/wtf/Platform.h @@ -306,6 +306,9 @@ || defined(ARM_ARCH_7R) #define WTF_ARM_ARCH_VERSION 7 +#elif defined(ARM_ARCH_8A) +#define WTF_ARM_ARCH_VERSION 8 + /* RVCT sets _TARGET_ARCH_ARM */ #elif defined(__TARGET_ARCH_ARM) #define WTF_ARM_ARCH_VERSION __TARGET_ARCH_ARM Similar patches should work on other Qt versions. Credits go to http://lists.buildroot.org/pipermail/buildroot/2017-August/200515.html, http://lists.buildroot.org/pipermail/buildroot/2017-August/200520.html

Hi, I'd recommend posting that question to the the QtWebEngine mailing list. You'll find there QtWebEngine's developers/maintainers. This forum is more user oriented.

@micland I thought of that but discarded the idea because Raspbian seems to be the de facto standard distribution for RPi, and IMHO the mkspec should work out-of-the-box with the Rasbian library paths. Or at least there should be a mkspec for Raspbian. Also, if I understand it right, the symlinks won't fix the run time error. (But I have to admit I am not at all sure I understand it right.) One thing that puzzles me is the big difference between RPi3 and RPi2 mkspecs. Wouldn't it be enough to change the processor optimization flags?

hi, i has same problem, i refresh raspberry, but issue also happen. please help me to solved issue. thanks u.

@hervir @Csaba911 Try CDP Studio instead. In less than 30 minutes I had a full graphical demo interface up and running on Pi3B+ with working touch screen and all. That was truly magically simple.