Re: appimages and windows issues
On 2023.05.23 17:31, Ingo Klöcker via KMyMoney-devel wrote: On Dienstag, 23. Mai 2023 01:37:39 CEST Jack via KMyMoney-devel wrote: > Next step. I have built kmymoney5, but trying to build the installer, > it says: > > buildinfo is broken... it says: > unresolvable: nothing provides mingw32(libgcc_s_sjlj-1.dll) needed by > mingw32-cross-nsis >nothing provides mingw32(libstdc++-6.dll) needed by > mingw32-cross-nsis >nothing provides mingw32(libwinpthread-1.dll) needed by > mingw32-cross-nsis >nothing provides mingw32(libz.dll) needed by mingw32-cross-nsis > > I can't tell why the 64 bit build is pulling in anything from mingw32. The payload of the installer may be a 64-bit build, but the installer (nsis) itself is a 32-bit application. libgcc_s_sjlj-1.dll is one of multiple exception libraries. It may need to be added explicitly to the installer. Are you building KMyMoney for Windows with Craft? I am trying to build KMyMoney for Windows in OBS on OpenSuse Tumbleweed in a VirtualBox VM. I don't believe Craft is involved there. See also https://bugzilla.opensuse.org/show_bug.cgi?id=1211586. If the KDE CI system is using Craft, then perhaps the problem does not exist there, as those builds have been succeeding (https://binary-factory.kde.org/job/KMyMoney_Release_win64/)
Re: appimages and windows issues
On Dienstag, 23. Mai 2023 01:37:39 CEST Jack via KMyMoney-devel wrote: > Next step. I have built kmymoney5, but trying to build the installer, > it says: > > buildinfo is broken... it says: > unresolvable: nothing provides mingw32(libgcc_s_sjlj-1.dll) needed by > mingw32-cross-nsis >nothing provides mingw32(libstdc++-6.dll) needed by > mingw32-cross-nsis >nothing provides mingw32(libwinpthread-1.dll) needed by > mingw32-cross-nsis >nothing provides mingw32(libz.dll) needed by mingw32-cross-nsis > > I can't tell why the 64 bit build is pulling in anything from mingw32. The payload of the installer may be a 64-bit build, but the installer (nsis) itself is a 32-bit application. libgcc_s_sjlj-1.dll is one of multiple exception libraries. It may need to be added explicitly to the installer. Are you building KMyMoney for Windows with Craft? Regards, Ingo signature.asc Description: This is a digitally signed message part.
Re: appimages and windows issues
On 2023.05.22 14:42, Jack via KMyMoney-devel wrote: On 2023.05.20 19:09, Jack via KMyMoney-devel wrote: On the "hanging" discussed on the user mailing list - I cannot replicate it, but the user now confirms that the master branch appimages do work for him, only the 5.1 branch appimages hang. I'm suspecting something related to Qt and WebEngine, but I still have no solid clues. On the Windows crashes - I'm trying to set up a local SUSE build system (in VirtualBox) but the instructions on the snapshots web page is apparently rather out of date. Hopefully I can puzzle it out, but if anyone can provide a quick update (just in an email if not actually updating the page) I'd appreciate it. I think I finally got a bit of a clue. The OSB Windows builds use mingw, so can't use QTWebEngine. However, trying to use QtWebKit (building either libalimia or kmymoney) it errors out with: buildinfo is broken... it says: unresolvable: nothing provides mingw64(icui18n56.dll) needed by mingw64-libqt5-qtwebkit nothing provides mingw64(icuuc56.dll) needed by mingw64-libqt5-qtwebkit These are the same errors I see looking at the OBS pages. Lots of searching suggests that the problem is a version mismatch between libqt5-qtwebkit and whatever package contains the icu libraries. However, while learning my way around zypper and yast, it looks like I had package mingw64-libicu61 installed from the mingw repository. Explicitly deleting that package (and the associated -devel one) has allowed the build to progress. I believe (but at this point am no longer certain) I had explicitly added the mingw64-libicu61 repository, so I don't know if this discovery can help with the actual OSB server configuration. Next step. I have built kmymoney5, but trying to build the installer, it says: buildinfo is broken... it says: unresolvable: nothing provides mingw32(libgcc_s_sjlj-1.dll) needed by mingw32-cross-nsis nothing provides mingw32(libstdc++-6.dll) needed by mingw32-cross-nsis nothing provides mingw32(libwinpthread-1.dll) needed by mingw32-cross-nsis nothing provides mingw32(libz.dll) needed by mingw32-cross-nsis I can't tell why the 64 bit build is pulling in anything from mingw32. I also know there is no real evidence, but I've been wondering if these two issues are somehow related. Jack
Re: appimages and windows issues
On 2023.05.20 19:09, Jack via KMyMoney-devel wrote: On the "hanging" discussed on the user mailing list - I cannot replicate it, but the user now confirms that the master branch appimages do work for him, only the 5.1 branch appimages hang. I'm suspecting something related to Qt and WebEngine, but I still have no solid clues. On the Windows crashes - I'm trying to set up a local SUSE build system (in VirtualBox) but the instructions on the snapshots web page is apparently rather out of date. Hopefully I can puzzle it out, but if anyone can provide a quick update (just in an email if not actually updating the page) I'd appreciate it. I think I finally got a bit of a clue. The OSB Windows builds use mingw, so can't use QTWebEngine. However, trying to use QtWebKit (building either libalimia or kmymoney) it errors out with: buildinfo is broken... it says: unresolvable: nothing provides mingw64(icui18n56.dll) needed by mingw64-libqt5-qtwebkit nothing provides mingw64(icuuc56.dll) needed by mingw64-libqt5-qtwebkit These are the same errors I see looking at the OBS pages. Lots of searching suggests that the problem is a version mismatch between libqt5-qtwebkit and whatever package contains the icu libraries. However, while learning my way around zypper and yast, it looks like I had package mingw64-libicu61 installed from the mingw repository. Explicitly deleting that package (and the associated -devel one) has allowed the build to progress. I believe (but at this point am no longer certain) I had explicitly added the mingw64-libicu61 repository, so I don't know if this discovery can help with the actual OSB server configuration. I also know there is no real evidence, but I've been wondering if these two issues are somehow related. Jack
