Be
That works, though the zenity/kdialog dependency needs to be clearly documented if (Async)MessageDialog is used.
Okay. I think it would help to explain this in a comment.
I am running into this bug using flatpak-builder: ``` Rewriting contents of org.mixxx.Mixxx.desktop Running appstream-compose Processing application org.mixxx.Mixxx Error loading AppData file: failed to parse /app/share/appdata/org.mixxx.Mixxx.appdata.xml: Error on line 265...
Ugly hack around this in the Flatpak manifest: ``` post-install: - sed -i 's///g' ${FLATPAK_DEST}/share/metainfo/org.mixxx.Mixxx.metainfo.xml - sed -i 's///g' ${FLATPAK_DEST}/share/metainfo/org.mixxx.Mixxx.metainfo.xml ```
Unfortunately it looks like this [isn't supported upstream with static linking](https://codereview.qt-project.org/gitweb?p=qt/qtbase.git;a=commitdiff;h=5b07f14a4ff6b08887473b1b583ee2f71dec6f76). From the commit message: > Although it has some limitations, with qt_internal_add_qml_module if it specifies non-public deps these won't...
It turns out this was not implemented upstream until recently. https://codereview.qt-project.org/c/qt/qtbase/+/405678 was merged to the Qt 6.3 branch 2022-04-12. According to https://wiki.qt.io/Qt_6.3_Release Qt 6.3.0 was released 2022-04-12 and Qt 6.3.1...
vcpkg already has Qt 6.3.1 as of #25259, however I do not see any `vcpkg_fixup_pkgconfig` calls in the Qt6 packaging scripts.
> In general you could try to use the qmake *.prl files to figure out what you require for linking. Oh, I didn't know about these. Is there a way...
It turns out that parsing the .qrl files was quite simple with this regex `^QMAKE_PRL_LIBS = (.*)$` then finding and replacing `$$[QT_INSTALL_PREFIX]` with the result of `qmake -query QT_INSTALL_PREFIX`. This...
AFAIK nothing has been done to fix this yet.