Bug 435753

Summary:	No aqbanking plugin available from binary factory
Product:	[Unmaintained] Craft	Reporter:	Ralf Habacker <ralf.habacker>
Component:	Blueprints	Assignee:	Hannah von Reth <vonreth>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	bcooksley, kde-windows
Priority:	NOR
Version:	stable
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Bug Depends on:
Bug Blocks:	435581

Description Ralf Habacker 2021-04-15 02:41:21 UTC

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

Comment 1 Ralf Habacker 2021-04-15 09:05:23 UTC

That issue need to be fixed by the craft/craft blueprint maintainers.

Comment 2 Ben Cooksley 2021-04-15 09:29:27 UTC

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.

Comment 3 Ralf Habacker 2021-04-17 19:03:06 UTC

(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.

Comment 4 Ben Cooksley 2021-04-17 19:13:16 UTC

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)

Comment 5 Ralf Habacker 2021-04-19 07:46:18 UTC

(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.

Comment 6 Ralf Habacker 2022-05-13 07:55:15 UTC

(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.

Comment 7 Ralf Habacker 2024-08-06 17:30:04 UTC

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.