> I tried to manually build the MySQL driver but failed because configure not > only looks for libmysql.* but also for a config.win32 (why).
I use the following patch for my builds: https://github.com/Martchus/ PKGBUILDs/blob/master/qt5-base/mingw-w64/0013-Fix-linking-against-shared- static-MariaDB.patch That works (the resulting package contains sqldrivers/qsqlmysql.dll). Note that the PostgreSQL needed a similar patch in my case. The only problem left is that it is currently not possible to use the static build of the MariaDB and Qt because mariadb-connector-c comes with its own pthread implementation which has conflicting symbols with the pthread library Qt uses. Am Freitag, 11. Oktober 2019, 10:27:47 CEST schrieb helmut.muel...@gmail.com: > Recently the Bug "MySQL plugin binaries are in commercial packages" > https://bugreports.qt.io/browse/QTBUG-76081 was closed. > > > This means that (starting with Qt-5.12.3, I think) it is not possible to > access MySQL or MariaDB databases with LGPL or commercial Qt versions. > > > I am using LGPL Qt. To avoid licensing problems I used the QtSQL plugin for > MySQL but replaced the MySQL libmysql.dll with libmariadb.dll (by renaming > the latter). > > > This does not work anymore because there is no sqldrivers/qsqlmysql.dll in > the binary LGPL distributions. > > > I tried to manually build the MySQL driver but failed because configure not > only looks for libmysql.* but also for a config.win32 (why). > > > Any ideas or hints for this? > > > Helmut > > > PS: The current Qt documentation does not mention the problems with MySQL. > > > PPS: Anybody out there looked at libdrizzle or libdrizzle-redux as an > alternative to qsqlmysql? _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
