Migrating Windows CI to Qt 6.7 - Roadblocks

[christoph at cullmann.io]

On 2024-05-27 14:55, Carl Schwan wrote:
> On Saturday, May 25, 2024 1:02:41 PM Central European Summer Time
> christoph at cullmann.io wrote:
>> Hi,
>> 
>> Thanks, you were faster than me.
>> 
>> Now that frameworks is QDBus free on Windows and macOS I would even
>> propose that in a next update of the stuff we really not have QtDBus
>> around at all on these systems and make the use optional for the apps
>> that want to support them.
>> 
>> We go to great lengths to avoid that dbus stuff is ever called, even
>> deleting the dll and the most freezes you will get if that is not done
>> is just dbus related.
>> 
>> It would be great if people could join the effort to get that right.
>> 
>> https://invent.kde.org/packaging/craft-blueprints-kde/-/issues/17
> 
> But what happens for projects that actually needs DBus for non-optional
> features e.g. Akonadi and the PIM apps? Dbus can't be ifdef there and I 
> am a
> bit worried that DBus support for Windows apps in Craft is going away.

I don't think we can remove that you can get DBus there,
I just would like that you need to explicitly add it to your blueprints
that need it and not just 'oh, I use KIO, I pull in DBus'.

IMHO the nicest way would be to have an extra qt-dbus lib you can depend 
on
in the blueprints.

Then KDE Connect and other parts that need it (and hopefully take care 
that
a session bus is packaged and starts) can have it, but e.g. Kate doesn't 
need
to start to blacklist stuff it not even depends on.

Greetings
Christoph

> 
> Cheers,
> Carl
> 
>> 
>> Greetings
>> Christoph
>> 
>> > Regards,
>> > Volker