dbus-less frameworks on osx

[Kevin Funk]

On Wednesday, May 11, 2016 7:38:58 AM CEST Martin Graesslin wrote:
> On Wednesday, May 11, 2016 4:00:45 AM CEST Nick Shaforostoff wrote:
> > hi all! I'm investigating possibility of getting some kde apps to build on
> > osx with vanilla Qt without dbus.
> > 
> > would you accept patches that make that possible?

+1

I looked into that a while ago, but quickly discarded the idea, because QtDBus 
was just so broadly used in KF5. Just checked again, and it appeared to me 
it's indeed doable, when skipping a few frameworks (see below).

FYI: Just scan frameworks for "include.+QDBus", you'll hits in the following 
repositories:

bluez-qt
kactivities
kactivities-stats
kauth
kbookmarks
kcmutils
kconfigwidgets
kdbusaddons
kded
kdelibs4support
kdnssd
kglobalaccel
khtml
kiconthemes
kinit
kio
kmediaplayer
knotifications
knotifyconfig
kservice
kwallet
kxmlgui
modemmanager-qt
networkmanager-qt
solid

bluez-qt, modemmanager-qt, networkmanager-qt are heavy users of QtDBus, but 
are normally not needed for the majority of our KDE apps. I'd leave them as-
is.

Solid is another heavy user, but only in the Linux-specific backends iiuc, so 
not a problem.

You'll have some fun getting kio to built without DBus, tons of uses of QtDBus 
there.

The other frameworks only use QtDBus in a few places, definitely possible to 
make them optional. A few of them are not needed on OS X/Windows anyway -- say 
kded, kactivities, etc. -- not sure if they need to be dbus-less.

IOW: Go ahead! :)

Cheers,
Kevin

> > 
> > for example, i have just built kauth without dbus and i can prepare a
> > review request with a (nice) patch for this
> 
> Having suggested this in the past: I think that's a good idea and I fully
> support it.
> 
> Cheers,
> Martin


-- 
Kevin Funk | kfunk at kde.org | http://kfunk.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20160511/4df51090/attachment.sig>