On Fri, May 15, 2015 at 8:14 AM, Rainer Schuetz <[email protected]> wrote: > Just a word of thanks again to Ray, Alexey and David for helping me with the > 5.3.2 build. It took a long time on my computer, but after a few attempts, > mainly due to my inexperience, it went through (32 and 64 bit).
Thank you very much for your feedback, it makes this stuff all the more worth doing. > > Maybe a few additional infos/remarks for somebody trying to do the same thing: > > - the most manual work is adjusting the patches to the state required for the > 5.3.2 build (they are adjusted to 5.4.1 now). A trick (thanks Alexey) can > save the work: go back in git-history of the qt5 package, copy the patches > from there, and overwrite the ones in the 5.4.1 version. A commit that > contains the right patches is: > > https://github.com/Alexpux/MINGW-packages/commit/415c383426be31c0d4edc270307a07e3f67b98a2 > > According to Alexey the 5.4 patches are good for use with 5.3.2 too (except > 42 and 44) > > - rather than installing e.g. to /opt/myqt532 I’d suggest a folder in > architecture-specific area, so either mingw32 or mingw64, or both (as in my > case) Yeah, I should've recommended that instead actually, but I wasn't sure if you cared about both architectures. > > - I did not experience any problems from which one could conclude that you > have to uninstall the current Qt version from msys2 to prevent problems > building the older version. > > - don’t forget to run qtbinpatcher after install ;) Normally the post install script would do this, if you install from the created pkg.xz files but I guess this wont work for different prefixes because the .install files are hardcoded with our standard prefixes. This is something I'd be happy to accept a patch to correct. It would rename qt5-{i686,x86_64}.install to qt5-{i686,x86_64}.install.in and then use sed in the PKGBUILD prepare() or package() function to transform a @PREFIX@ token in those, creating the final qt5-{i686,x86_64}.install) > > - once you’re done, if you build with cmake you’ll likey bump into two tiny > problems: > > one is a known typo in qt532 in the file > > .../lib/camke/Qt5Core/Qt5CoreMacros.cmake - you need to replace COPY_ONLY > with COPYONLY Ideally this should be submitted to upstream Qt-Project if they've not already fixed it. > > the other is some accessibility library is tried to be loaded twice. > Unfortunataly I forgot the exact filename, but I think deleting the file > .../lib/cmake/Qt5Core/Qt5AccessibilityConfig.cmake (or similar, a file that > doesn’t exist in stock Qt5) solves this Weird! Not sure what's going on with that. > > Thanks again to Alexey and David for their patience with my inexperience on > IRC, and of course Ray for getting me going. > > Best > .r. > > >> On 12 May 2015, at 12:52, Ray Donnelly <[email protected]> wrote: >> >> You know you dropped the mailing list here? I don't mind, since what >> I'm going to write isn't much use generally. >> >> .. building Qt5 from the PKGBUILD with makepkg-mingw is much simpler >> than building Qt yourself by hand .. esp. once you get into the swing >> of it, because we've spent a long time solving the problems you'll run >> into otherwise. >> >> On Tue, May 12, 2015 at 12:45 PM, Rainer Schuetz <[email protected]> wrote: >>> Thanks Ray, for this detailed description. It sounds like the way to go, as >>> that way all packages would be made with the same toolchain. But not >>> exactly simple ;) Hopefully I’ll manage. >>> >>> This morning I saw that Qt 5.4.2 is basically done, so I am currently >>> trying to build with a 5.4.2 snapshot from stock Qt. >>> >>> Our bug is not well understood. It’s quite difficult to debug because it >>> involves communication between different executables through the network, >>> using OSC. The closest we got is that something goes wrong when Qt >>> interacts with yaml-cpp to send strings to another executable. Basically we >>> just know it seems to work with 5.3.2 and it definitely does not work with >>> 5.4.1 :) >>> >>> Thanks a lot sofar! >>> .r. >>> >>> >>>> On 12 May 2015, at 12:08, Ray Donnelly <[email protected]> wrote: >>>> >>>> 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 ------------------------------------------------------------------------------ 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
