435753 2021-04-15 02:41:21 +0000 No aqbanking plugin available from binary factory 2024-08-06 17:30:04 +0000 1 1 10 Unmaintained Craft Blueprints stable Microsoft Windows Microsoft Windows RESOLVED WONTFIX NOR normal --- 435581 0 ralf.habacker vonreth bcooksley windows-bugs-null 0 oldest_to_newest 2025185 0 ralf.habacker 2021-04-15 02:41:21 +0000 SUMMARY The preview builds for Windows listed at https://kmymoney.org/download.html does not provide the aqbanking plugin. STEPS TO REPRODUCE 1. download and unpack a portable package from the listed web page 2. start kmymoney 3. open settings menu OBSERVED RESULT There is no entry for the aqbanking plugin EXPECTED RESULT There should be an entry for the aqbanking plugin SOFTWARE/OS VERSIONS Windows: 10 2025254 1 ralf.habacker 2021-04-15 09:05:23 +0000 That issue need to be fixed by the craft/craft blueprint maintainers. 2025260 2 bcooksley 2021-04-15 09:29:27 +0000 The issue here is that AQBanking appears to rely on an autotools build system. https://invent.kde.org/packaging/craft-blueprints-kde/-/blob/master/libs/_autotools/aqbanking/aqbanking.py You therefore have two options: 1) Request that the Binary Factory build be switched to be MingW based - which can handle autotools builds. 2) Prepare a build system port that allows for AQBanking to be built using CMake natively Note that MingW does not support QtWebEngine - so you will have to be able to function without a web rendering engine to use MingW. 2025770 3 ralf.habacker 2021-04-17 19:03:06 +0000 (In reply to Ben Cooksley from comment #2) > 2) Prepare a build system port that allows for AQBanking to be built using > CMake natively That belongs also to the gwenhywfar package. 2025773 4 bcooksley 2021-04-17 19:13:16 +0000 Note that as KMyMoney is one of the only users of those two packages, the work in this case should be done by KMyMoney contributors (who also have to choose which of the two presented roads you wish to go down) 2026036 5 ralf.habacker 2021-04-19 07:46:18 +0000 (In reply to Ben Cooksley from comment #4) > Note that as KMyMoney is one of the only users of those two packages, the > work in this case should be done by KMyMoney contributors (who also have to > choose which of the two presented roads you wish to go down) The content on the https://www.aquamaniac.de/rdm/projects/aqbanking/wiki/Gwbuild page may shed some light on the available options. 2123115 6 ralf.habacker 2022-05-13 07:55:15 +0000 (In reply to Ralf Habacker from comment #5) >> https://www.aquamaniac.de/rdm/projects/aqbanking/wiki/Gwbuild page may shed >> some light on the available options. > meson is another good alternative since it also uses ninja and is therefore also extremely fast. But I wasn't able to > adapt my projects to use "meson" because some features I needed for e.g. AqFinance or AqBanking required a version of meson newer > than what is provided by the distribution I'm currently working with. For this approach, Martin Preuss has set up a corresponding branch https://www.aquamaniac.de/rdm/projects/aqbanking/repository/revisions/mp-20190307-meson/show. 2343601 7 ralf.habacker 2024-08-06 17:30:04 +0000 The maintainer of aqbanking/gwenhywfar does not want to migrate to cmake and according to https://bugs.kde.org/show_bug.cgi?id=435581#c11 you cannot build aqbanking with msvc.