On Tue, May 12, 2015 at 12:32 AM, Rainer Schuetz <[email protected]> wrote: > Hi All, > > Because of problems with Qt5.4.1 we are for the time being forced to use > Qt5.3.2 in our project. In Linux we can download Qt-versions different from > the ones supplied by the distribution and integrate them in the build via the > cmake variable CMAKE_PREFIX_PATH set to the root of the Qt tree.
What problems are these? Are there bug reports on qt.io for them? Or better, patches we can merge with our qt5 (though with 5.5 so close we'd probably see if they're fixed in that version instead). > > I thought I'd give it try to assemble a Qt5.3.2 tree that can be used for > building without having to interfere with the actual msys2 system. I put all > the dll’s into the Qt bin folder and just in case also added the others in > lib/include etc. This seems to work, although I haven’t tested it extensively > yet. The additional packages needed seem to be these (32-bit): > > mingw-w64-i686- > > gcc-libs-4.9.1-6-any > icu-54.1-3-any > pcre-8.36-1-any > zlib-1.2.8-4-any > > Have others tried to assemble such “artificial” Qt trees, that integrate > dependencies, for building? Are there hidden dangers, or things I could do > better? Hi Rainer, I'd use our mingw-w64-qt5 folder ( https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-qt5 ) as your starting point; copy all of those files into a new folder, mingw-w64-qt5-my532. Update your system to the latest packages as usual, install base-devel Then modify the PKGBUILD as follows: 1. Rename package name so that it doesn't conflict with other Qt5-using stuff you may use or get updated next time you update, so e.g.: pkgname="${MINGW_PACKAGE_PREFIX}-${_realname}-my532" 2. Downgrade the version number: _ver_base=5.3.2 3. Change the prefix so that it doesn't conflict with our Qt5, same as we do for mingw-w64-qt5-static: ... (around line 51) else _qt5_prefix="/opt/qt532" fi From an msys2_shell.bat launched shell, in that folder: Run updpkgsums Run makepkg-mingw -sLf Some patches may fail, either correct them or if they're > 5.3.2 specific, disable them in the PKGBUILD and re-run. This will generate you a .pkg.xz file that you can use on any other updated MSYS2 installation. Cheers, Ray. > > Thanks! > Rainer > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Msys2-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/msys2-users ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
