android-ndk/default | ||
angleproject/mingw-w64 | ||
arch-repo-manager/git | ||
assimp/mingw-w64 | ||
baikal/default | ||
bashmarks/custom | ||
bento4/default | ||
binutils/mingw-w64-symlinks | ||
blackwidowcontrol | ||
bluetooth-raspberrypi | ||
boost | ||
brother-mfc-j4410dw/default | ||
brotli/mingw-w64 | ||
bzip2/static | ||
c++utilities | ||
ccache | ||
cmake | ||
cmake-format/default | ||
configure/mingw-w64 | ||
cppunit | ||
dbus/static | ||
dbus-soundrecorder/default | ||
dcadec/mingw-w64 | ||
devel | ||
devtools/custom | ||
diriterator/default | ||
essentia/git | ||
evince/mingw-w64 | ||
exorciser/default | ||
expat/static | ||
extra-cmake-modules/mingw-w64 | ||
ffmpeg | ||
filezilla | ||
fontconfig/static | ||
freetype2 | ||
freetype2-bootstrap | ||
gdk-pixbuf2/mingw-w64 | ||
geany/mingw-w64 | ||
genesis-starter/default | ||
geocoordinatecalculator | ||
gerbera/default | ||
gettext/mingw-w64 | ||
git-codereview/default | ||
gitea/default | ||
github-release/gdm85-git | ||
glib2 | ||
gnome-breeze/git | ||
gnutls/mingw-w64 | ||
gogs/default | ||
graphite/static | ||
gsm/mingw-w64 | ||
gtk3/mingw-w64 | ||
handbrake/libfdk_aac | ||
harfbuzz | ||
hopper/default | ||
indicator-kdeconnect/git | ||
isoviewer/default | ||
jangouts/default | ||
janus-gateway/default | ||
jflap/default | ||
kdeconnect/git | ||
kernel-backup-hooks/default | ||
keyutils/static | ||
kirigami2 | ||
libb2/static | ||
libdvdread/default | ||
libffi/static | ||
libfilezilla | ||
libgcrypt/static | ||
libglvnd/static | ||
libgpg-error/static | ||
libice/static | ||
libiconv | ||
libpng/static | ||
libsm/static | ||
libsoxr/mingw-w64 | ||
libssh/mingw-w64 | ||
libx11/static | ||
libxau/static | ||
libxcb/static | ||
libxdmcp/static | ||
libxext/static | ||
libxkbcommon/static | ||
libxml2/static | ||
ltunify/default | ||
lz4/static | ||
mariadb-connector-c/mingw-w64 | ||
mediaplayerctl/default | ||
mediawriter/default | ||
meson/mingw-w64 | ||
midifile/git | ||
mkvtoolnix/git | ||
mpv/mingw-w64 | ||
mxedeployqt/git | ||
nettle/mingw-w64 | ||
networkmanager-sstp/default | ||
nginx/custom | ||
nginx-mod-accesskey/default | ||
nginx-mod-cache-purge/default | ||
nginx-mod-dav-ext/default | ||
nginx-mod-fancyindex/default | ||
nginx-mod-rtmp/default | ||
nginx-mod-slowfs-cache/default | ||
nginx-mod-substitutions-filter/default | ||
nginx-mod-upload-progress/default | ||
nginx-mod-upstream-fair/default | ||
okular/git | ||
openelec-dvb-firmware | ||
openocd | ||
openssl | ||
openssl-1.0/mingw-w64 | ||
osxcross/apple-darwin | ||
p11-kit/mingw-w64 | ||
passwordfile | ||
passwordmanager | ||
pcre/static | ||
pcre2 | ||
pdfmerge/default | ||
php73/default | ||
pi-fm-rds/git | ||
pistache/git | ||
plasma-sdk/default | ||
plasma-wayland-session-no-dbus/default | ||
plasma5-applets-thermal-monitor/git | ||
plasmoidviewer-debug/default | ||
pocketsphinx/default | ||
poedit/default | ||
postgresql/mingw-w64 | ||
proto-quic/mingw-w64-git | ||
psi/git | ||
python-colorzero/git | ||
python-gpiozero | ||
python-pyusb/default | ||
python-raspberry-gpio/default | ||
python-rpi.gpio/default | ||
python-spidev/default | ||
qca-qt5/mingw-w64 | ||
qemu-binfmt-arm/default | ||
qmplay2/default | ||
qpaeq-menu-entry/default | ||
qsyncthingtray/default | ||
qt5 | ||
qt5-3d | ||
qt5-activeqt/mingw-w64 | ||
qt5-base | ||
qt5-canvas3d | ||
qt5-charts | ||
qt5-connectivity | ||
qt5-datavis3d | ||
qt5-declarative | ||
qt5-gamepad | ||
qt5-graphicaleffects | ||
qt5-imageformats | ||
qt5-location | ||
qt5-multimedia | ||
qt5-networkauth | ||
qt5-quickcontrols | ||
qt5-quickcontrols2 | ||
qt5-remoteobjects | ||
qt5-script | ||
qt5-scxml | ||
qt5-sensors | ||
qt5-serialport | ||
qt5-speech | ||
qt5-svg | ||
qt5-tools | ||
qt5-translations | ||
qt5-virtualkeyboard | ||
qt5-webchannel | ||
qt5-webengine | ||
qt5-webglplugin | ||
qt5-websockets | ||
qt5-winextras | ||
qt5-xmlpatterns | ||
qt6-3d | ||
qt6-5compat | ||
qt6-activeqt | ||
qt6-base | ||
qt6-charts | ||
qt6-datavis3d | ||
qt6-declarative | ||
qt6-imageformats | ||
qt6-lottie | ||
qt6-networkauth | ||
qt6-quick3d | ||
qt6-quickcontrols2 | ||
qt6-quicktimeline | ||
qt6-scxml | ||
qt6-shadertools | ||
qt6-svg | ||
qt6-tools | ||
qt6-translations | ||
qt6-virtualkeyboard | ||
qt6-wayland/default | ||
qt6ct/default | ||
qtforkawesome | ||
qtutilities | ||
rapidjson | ||
reflective-rapidjson | ||
repoindex | ||
roccat-tools/default | ||
rpi_ws281x/git | ||
sphinxbase/default | ||
sqlite/mingw-w64 | ||
sqlpp11/default | ||
sstp-client/default | ||
subtitlecomposer | ||
syncthingtray | ||
system-image/android-arm64-v8a | ||
systray-memory-display/git | ||
tageditor | ||
tagparser | ||
toggletouch/default | ||
ttf-consolas/default | ||
ttf-oxygen/default | ||
ubuntu-latex-fonts/git | ||
util-linux/static | ||
vid.stab/mingw-w64 | ||
videodownloader | ||
vlc/nightly | ||
warmux/default | ||
wayland/static | ||
wxwidgets/mingw-w64 | ||
x264 | ||
x265/mingw-w64 | ||
xcb-util/static | ||
xcb-util-image/static | ||
xcb-util-keysyms/static | ||
xcb-util-renderutil/static | ||
xcb-util-wm/static | ||
xvidcore/mingw-w64 | ||
xz/static | ||
zstd/static | ||
zuki-themes/git | ||
.gitignore | ||
.gitmodules | ||
LICENSE | ||
README.md |
PKGBUILDs
Contains PKGBUILD files for creating Arch Linux packages:
- Packages for my own applications and libraries such as Syncthing Tray, Tag Editor, Password Manager, ...
- Packages I maintain in the AUR:
- misc packages, eg. Subtitle Composer, openelec-dvb-firmware, Jangouts
mingw-w64-*
packages which allow to build for Windows under Arch Linux, eg. FreeType 2, Qt 5 and Qt 6*-static
packages containing static librariesandroid-*
packages which allow to build for Android under Arch Linux, eg. iconv, Boost, OpenSSL, CppUnit, Qt 5 and Kirigamiapple-darwin-*
packages which allow to build for MaxOS X under Arch Linux, eg. osxcross and Qt 5 (still experimental)
- Other packages imported from the AUR to build with slight modifications
So if you like to improve one of my AUR packages, just create a PR here.
Binary repository
I also provide a binary repository containing the packages found in this repository and a lot of packages found in the AUR:
[ownstuff-testing]
SigLevel = Optional TrustAll
Server = https://martchus.no-ip.biz/repo/arch/$repo/os/$arch
Server = https://ftp.f3l.de/~martchus/$repo/os/$arch
[ownstuff]
SigLevel = Optional TrustAll
Server = https://martchus.no-ip.biz/repo/arch/$repo/os/$arch
Server = https://ftp.f3l.de/~martchus/$repo/os/$arch
The testing repository is required if you have the official testing repository enabled. (Packages contained by ownstuff-testing are linked against packages found in the official testing repository.)
The repository is focusing on x86_64 but some packages are also provided for i686 and aarch64.
Note that I can not assure that required rebuilds always happen fast enough (since the offical developers obviously don't wait for me before releasing their packages from staging).
Requests regarding binary packages can be tracked on the issue tracker of this GitHub project as well, e.g. within the general discussion issue.
Docker image
Checkout the repository docker-mingw-qt5.
Structure
Each package is in its own subdirectoy:
default-pkg-name/variant
where default-pkg-name
is the default package name (eg. qt5-base
) and
variant
usually one of:
default
: the regular packagegit
/svn
/hg
: the development versionmingw-w64
: the Windows version (i686/dw2 and x86_64/SEH)android-{aarch64,armv7a-eabi,x86-64,x86}
: the Android version (currently only aarch64 actively maintained/tested)apple-darwin
: the MacOS X version (still experimental)
The repository does not contain .SRCINFO
files.
Generated PKGBUILDs
To avoid repetition some PKGBUILDs are generated. These PKGBUILDs are determined
by the presence of the file PKGBUILD.sh.ep
besides the actual PKGBUILD
file.
The PKGBUILD
file is only present for read-only purposes in this case - do
not edit it manually. Instead, edit the PKGBUILD.sh.ep
file and invoke
devel/generator/generate.pl
. This requires the perl-Mojolicious
package to
be installed. Set the environment variable LOG_LEVEL
to adjust the log level
(e.g. debug
/info
/warn
/error
). Template layouts/fragments are stored
within generator/templates
.
Documentation about the used templating system
Contributing to patches
Patches for most packages are managed in a fork of the project under my GitHub
profile. For instance, patches for mingw-w64-qt5-base
are managed at
github.com/Martchus/qtbase.
I usually create a dedicated branch for each version, eg. 5.10.1-mingw-w64
. It
contains all the patches based on Qt 5.10.1. When doing fixes later on, I
usually preserve the original patches and create a new branch, eg.
5.10.1-mingw-w64-fixes
.
So in this case it would make sense to contribute directly there. To fix an existing patch, just create a fixup commit. This (unusual) fixup workflow aims to keep the number of additional changes as small as possbile.
To get the patches into the PKGBUILD files, the script
devel/qt5/update-patches.sh
is used.
Mass rebasing of Qt patches
This is always done by me. Please don't try to help here because it will only cause conflicts. However, the workflow is quite simple:
- Run
devel/qt5/rebase-patches.sh
on all Qt repository forks or justdevel/qt5/rebase-all-patches.sh
- eg.
rebase-patches.sh 5.11.0 5.10.1 mingw-w64-fixes
to create branch5.11.0-mingw-w64
based on5.10.1-mingw-w64-fixes
- after fixing possible conflicts, run
devel/qt5/continue-rebase-patches.sh
- otherwise, that's it
- all scripts need to run in the Git repository directory of the Qt module
except
rebase-all-patches.sh
which needs the environment variableQT_GIT_REPOS_DIR
to be set
- eg.
- Run
devel/qt5/update-patches.sh
ordevel/qt5/update-all-patches.sh
to update PKGBUILDs- eg.
devel/qt5/update-all-patches.sh "" mingw-w64 qt6
to consider all mingw-w64-qt6-* packages
- eg.
Brief documentation about mingw-w64-qt packages
The Qt project does not support building Qt under GNU/Linux when targeting mingw-w64. With Qt 6 they also stopped 32-bit builds. They also don't provide static builds the mingw-w64 target. They are also relying a lot on their bundled libraries while my builds aim to build dependencies separately. So expect some rough edges when using my packaging.
Neverthless it make sense to follow the official documentation. For concrete
examples how to use this packaging with CMake, just checkout the mingw-w64
variants of e.g. syncthingtray
within this repository. The Arch Wiki also has
a section about mingw-w64
packaging.
Note that the ANGLE and "dynamic" variants of Qt 5 packages do not work because
they would require fxc.exe
to build.
Tested build and deployment tools for mingw-w64-qt5 packages
Currently, I test with qmake and CMake. With both build systems it is possible to use either the shared or the static libraries. Please read the comments in the PKGBUILD file itself and the pinned comments in the AUR for futher information.
There are also pkg-config files, but those aren't really tested.
qbs and windeployqt currently don't work very well (see issues). Using the static libraries or mxedeployqt might be an alternative for windeployqt.
Tested build and deployment tools for mingw-w64-qt6 packages
In order to build a Qt-based project using mingw-w64-qt6 packages one also needs
to install the regular qt6-base
package for development tools such as moc. The
packages qt6-tools
and qt6-declarative
contain also native binaries which
might be required by some projects. At this point the setup can break if the
version of regular packages and the versions of the mingw-w64 packages differ. I
cannot do anything about it except trying to upgrade the mingw-w64 packages as
fast as possible. There's actually a lengthy discussion about this topi on the
[Qt development
mailinglist](https://lists.qt-project.org/pipermail/development/2021-September/
041732.html) so the situation might improve in the future.
Currently, I test only CMake. It is possible to use either the shared or the
static libraries. The static libraries are installed into a nested prefix
(/usr/i686-w64-mingw32/static
and /usr/x86_64-w64-mingw32/static
) so this
prefix needs to be prepended to CMAKE_FIND_ROOT_PATH
for using the static
libraries. To generally prefer static libraries one might use the helper scripts
provided by the mingw-w64-cmake-static
package.
The build systems qbs and qmake are not tested. It looks like Qt's build system does not install pkg-config files anymore and so far no effort has been taken to enable them.
Note that windeployqt needed to be enabled by the official/regular qt6-tools
package but would likely not work very well anyways. Using the static libraries
or mxdeployqt might be an alternative for windeployqt.
Static plugins and CMake
Qt 5 initially didn't support it so I added patches to make it work. After Qt 5 added support I still kept my own version because I didn't want to risk any regressions (which would be tedious to deal with). So the official documentation does not apply to my packages. One simply has to link against the targets of the wanted static plugins manually.
However, for Qt 6 I dropped my patches and the official documentation applies. I
would still recommended to set the target property QT_DEFAULT_PLUGINS
of
relevant targets to 0
and link against wanted plugin targets manually. At
least in my cases the list of plugins selected by default seemed needlessly
long. I would also recommended to set the CMake variable
QT_SKIP_AUTO_QML_PLUGIN_INCLUSION
to a falsy value because this pulls in a lot
of dependencies which are likely not needed.
Further documentation
The directory qt5-base/mingw-w64
contains also a README with more Qt 5
specific information.
Running Windows executables built using mingw-w64 packages with WINE
It is recommended to use the scripts x86_64-w64-mingw32-wine
and
i686-w64-mingw32-wine
provided by the mingw-w64-wine
package. These scripts
are a wrapper around the regular wine
binary ensuring all the DLLs provided by
mingw-w64-*
-packages of the relevant architecture can be located. It also uses
a distinct wine
prefix so your usual configuration (e.g. tailored to run
certain games) does not go into the way and is also not messed with.
Here are neverthless some useful hints to run WINE manually:
- Set the environment variable
WINEPREFIX
to use a distinct WINE-prefix if wanted. - Set
WINEPATH
for the search directories of needed DLLs, e.g.WINEPATH=$builds/libfoo;$builds/libbar;/usr/x86_64-w64-mingw32
. - Set
WINEARCH
towin32
for a 32-bit environment (win64
is the default which will get you a 64-bit environment) - Set
WINEDLLOVERRIDES
to control loading DLLs, e.g.WINEDLLOVERRIDES=mscoree,mshtml=
disables the annoying Gecko popup. - To set environment variables like
PATH
orQT_PLUGIN_PATH
for the Windows program itself use the following approach:- Open
regedit
- Go to
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment
- Add/modify the variable, e.g. set
PATH=C:\windows\system32;C:\windows;Z:\usr\x86_64-w64-mingw32\bin
andQT_PLUGIN_PATH=Z:/usr/x86_64-w64-mingw32/lib/qt6/plugins
- Open
- It is possible to run apps in an headless environment but be aware that WINE is not designed for this. For instance, when an application crashes WINE still attempts to show the crash window and the application stays stuck in that state.
- See https://wiki.winehq.org/Wine_User's_Guide for more information
Static GNU/Linux libraries
This repository contains several *-static
packages providing static libraries
intended to distribute "self-contained" executables. These packages are still
experimental and are not be regularily updated at this point.
It would conceivable to build even Qt as a static library and make even a fully statically linked executable. However, it would not be possible to support OpenGL because glvnd and vendor provided OpenGL libraries are always dynamic libraries. It is also not clear whether it makes sense to link against libc and X11/Wayland client libraries statically. Maybe it makes sense to aim for a partially statically linked build instead where libc/OpenGL/X11/Wayland are assumed to be provided by the GNU/Linux system but other libraries like Qt are linked against statically. This would be similar to AppImage where a lot of libraries are bundled but certain "core libraries" are expected to be provided by the system.
Note that I decided to let static libraries live within the subprefix
/usr/static
(in contrast to packages found in the AUR). The reason is that the
version might not be kept 100 % in sync with the shared counterpart. Hence it
makes sense to make the static packages independent with their own headers and
configuration files to avoid problems due to mismatching versions. Besides, some
projects (such as Qt) do not support installing shared and static libraries
within the same prefix at the same time because the config files would clash.