Melroy van den Berg
Melroy van den Berg
I think this ticket is really resonating with my ticket here: https://github.com/mxe/mxe/issues/2705. Thank you for bring this up again! My exact problem as well.
I hope so. Especially when gtk3 pull request is getting merged (https://github.com/mxe/mxe/pull/2788), it's merged now!
Well the root-cause is there is some kind of conflict: `virtual ULONG CLocalProgress::Release()' causes a section type conflict with 'ULONG CLocalProgress::[email protected]()'`
Did you also try the latest release? https://download.qt.io/official_releases/qt-installer-framework/4.3.0/installer-framework-opensource-src-4.3.0.tar.xz Since 3.2.2 version is from March 2020
Yea, so the src/qtifw-1-fixes.patch file contains additional software patches applied to the source code. Before the build starts. Due to the new version I expect it can't apply the path...
In my case the build fails earlier, during the `qtdeclarative-everywhere` dependency. So dependency tree is: `qtifw -> qttools -> qtdeclarative` ```sh make[4]: Leaving directory '/opt/mxe/tmp-qtdeclarative-i686-w64-mingw32.static/qtdeclarative-everywhere-src-5.15.3/tools/qmltestrunner' make[3]: *** [Makefile:284: sub-qmltestrunner-make_first] Error...
Hm indeed. This is strange indeed. I created an upstream issue in Jira: https://bugreports.qt.io/browse/QTIFW-2564
@tonytheodore If this is a (cache) variable I would expect you just can use `-D variable_name=value` during a meson configure or meson setup step.
Indeed, the example of using multiple compose files is a bit strange. The whole purpose of Docker compose is to use a single file, eg. containing postgres with a dependency...
Are we synapse yet?