Arch Linux User Repository

Who flagged this package (or wants to flag it): The KDE patch branch doesn't seem rebased yet and the regular qt5-base package has not been updated as well. Since this package is using the KDE patch branch I'm going to wait for them to rebase. You generally don't need to flag the package as I'm subscribed to relevant Qt mailing lists anyways.

I've been updating this package and some further modules to use patches from KDE's fork. This is in accordance with the native Qt packages. As far as I know KDE's fork is not tagging releases. However, I will not pick up every single new commit on their branch but only update the package when it is worth it. Only flag the package as out-of-date if there are patches on their branch which are generally very important.

Notes regarding 5.15.1 update

• With this update I finally splitted all static libraries from further Qt repositories into their own packages as well. So now there's not only mingw-w64-qt5-base-static but also mingw-w64-qt5-svg-static, mingw-w64-qt5-declarative-static and so on. The static version is still sharing files with the shared version and as such depends on the shared packages. However, this change allows to avoid building all the static libraries if only shared libraries are required. If you've so far used static libraries from further Qt modules be sure to install the additional *-static packages.
• Otherwise there were not much build system changes on the Qt side so I don't think this update broke much.
• As stated in the sticky comment I'm thinking about Qt 6 packaging but this also means I'm not going to take much effort to address any outstanding bugs/limitations for the Qt 5 packages anymore (broken ANGLE build, build Qt WebEngine, …).
• This is the last official release of the 5.x. Let's see whether further updates for the 5.x branch will be made available by the community. If the regular qt5-base packages picks up such commits I could update this package here as well.

Before upgrading, be sure to remove the old version of the package from your system. Preferably, build the package in a clean chroot using makechrootpkg.

Also, please read the other comments and issues on GitHub for known bugs and limitations.

There also exist a binary repository: https://martchus.no-ip.biz/repo/arch/ownstuff, https://wiki.archlinux.org/index.php/Unofficial_user_repositories#ownstuff

@theone74 It is currently not possible to use the MariaDB plugin with the static version of Qt because mariadb-connector-c comes with its own pthread implementation which has conflicting symbols with the pthread library Qt uses. Since some PostgreSQL update the same is true for the PostgreSQL plugin.

So you have to disable the plugin. When using CMake, plugins are not be automatically added so you should not run into the issue by default. When using qmake you need to disable the plugin manually, eg. you can add the following arguments to enable only the plugins which actually work:

CONFIG+=no_smart_library_merge QTPLUGIN.sqldrivers=qsqlite QTPLUGIN.sqldrivers+=qsqlodbc CONFIG+=static

(https://github.com/Martchus/PKGBUILDs/blob/master/qt5-tools/mingw-w64-static/PKGBUILD#L45)

All my packages are managed at GitHub where you can also contribute directly: https://github.com/Martchus/PKGBUILDs

Patches for this package are managed at: https://github.com/Martchus/qtbase/tree/5.11.0-mingw-w64
if you like to contribute to patches, read this: https://github.com/Martchus/PKGBUILDs/#contributing-to-patches

If you would like to contribute, here is a list of known bugs and things needing improvement:

• The linker library search paths for applications which need to be build for the host architecture aren't set correctly. Hence those paths are currently set manually which is quite hacky. Affected packages are mingw-w64-qt5-declarative and mingw-w64-qt5-tools and (also the apple-darwin versions).
• Compiling QtAV using the ANGLE version doesn't work. I don't know whether other applications/libs using OpenGL via Qt are also affected but it is very likely.
• Updating mingw-w64-qt5-webkit to ng version.
• See also https://github.com/Martchus/PKGBUILDs/issues

Also note the comments about the different variants inside the PKGBUILD itself.

I'd like to give fixing https://github.com/Martchus/PKGBUILDs/issues/86 a few more days before rebuilding everything. If you can't wait for 5.12.2, patches are actually already rebased: https://github.com/Martchus/PKGBUILDs/tree/update/qt5

(Checksums have not been updated yet on this WIP branch.)

I'm currently in the process of updating to 5.12.1.

Seems they added some changes to the build system which conflict with my effort for making a fully statically linked executable relying on "system libraries" rather than bundles ones. I suppose most of my patches are adapted now. Some workarounds even might be no longer necessary but I also had to add new workarounds. At least it seems not totally messed up so far. I could do a static build of all the tools from the qttools repo (qmake) and of my Syncthing Tray application (CMake).

I noticed that a recent update of the mingw-w64-postgresql package apparently broke the static PostgreSQL plugin. The reason for the breakage seems the same as for the static MySQL plugin. (See pinned comment.)

And I had to fix windeployqt. It seems upstream really doesn't care about cross-compilation for Windows. But at least that patch might be upstream-able.

Update to 5.11.2 is delayed by https://aur.archlinux.org/packages/mingw-w64-glib2/#comment-663726.

@alexzk The dependency structure is not different from the regular qt5-base package in that regard. Don't use stupid AUR helper - at least not here. To ease bootstrapping I created mingw-w64-freetype2. There's also my binary repository if you don't want to care about bootstrapping at all.

It does circular dependency somewhere in harfbuzz/freetype2 etc. Just tries install stuff in loop.

@Martchus No. I just manually compare the version of mingw-w64 packages with the latest upstream version. Thanks for the patch!

@adsun Added the patch. Btw, do you have a script to flag mingw-w64 packages (just because you flag my packages so often/fast)?

The build now fails during the qmake build with glibc version 2.28. The native linux qt5 package has a patch that fixes this problem.

@luntik2012 "Before upgrading, be sure to remove the old version of the package from your system. Preferably, build the package in a clean chroot using makechrootpkg." Did you follow this instruction?

i686-w64-mingw32-g++ -g -shared -Wl,-subsystem,windows -Wl,--out-implib,/tmp/yaourt-tmp-nick/aur-mingw-w64-qt5-base/src/build-i686-w64-mingw32/lib/libQt5Gui.dll.a -o ../../lib/Qt5Gui.dll object_script.Qt5Gui.Release -lcomdlg32 -loleaut32 -limm32 -lwinmm -lws2_32 -lole32 -luuid -ladvapi32 -ljpeg -lpng -L/usr/i686-w64-mingw32/lib -lharfbuzz -lfreetype -lglu32 -lopengl32 -lgdi32 -luser32 -L/tmp/yaourt-tmp-nick/aur-mingw-w64-qt5-base/src/build-i686-w64-mingw32/lib /usr/i686-w64-mingw32/lib/libQt5Core.dll.a -lpng -lharfbuzz -lz ./.obj/release/qtextengine.o:/tmp/yaourt-tmp-nick/aur-mingw-w64-qt5-base/src/qtbase-everywhere-src-5.11.0/include/QtCore/../../src/corelib/tools/qstringview.h:270: undefined reference to `_imp___ZN9QtPrivate13isRightToLeftE11QStringView' collect2: error: ld returned 1 exit status make[3]: [Makefile.Release:1183: ../../lib/Qt5Gui.dll] Error 1 make[3]: Leaving directory '/tmp/yaourt-tmp-nick/aur-mingw-w64-qt5-base/src/build-i686-w64-mingw32/src/gui' make[2]: [Makefile:36: release] Error 2 make[2]: Leaving directory '/tmp/yaourt-tmp-nick/aur-mingw-w64-qt5-base/src/build-i686-w64-mingw32/src/gui' make[1]: [Makefile:523: sub-gui-make_first] Error 2 make[1]: Leaving directory '/tmp/yaourt-tmp-nick/aur-mingw-w64-qt5-base/src/build-i686-w64-mingw32/src' make: [Makefile:45: sub-src-make_first] Error 2 ==> ERROR: A failure occurred in build().