Windows: Make sure we don't start/use dbus-daemon
Closed, ResolvedPublic

Description

Still not entirely sure what triggers the startup of dbus-daemon (it's not us, nor KF5).

Things to do:

  • Introduce an env var, like KDEV_NO_DBUS
  • Don't use any of the QDBus* classes if this env var is set
kfunk created this task.Jan 21 2016, 8:09 AM
kfunk updated the task description. (Show Details)
kfunk raised the priority of this task from to Needs Triage.
kfunk added a project: KDevelop.
kfunk added a subscriber: kfunk.
kfunk added a comment.Jan 29 2016, 9:11 AM

We should also use QtSingleApplication for implementing the "open file in running KDevelop session" feature.

Approach:
[10:08:18] <kfunk> let KDevelopApplication inherit from QtSingleApplication instead of QApplication (and add a bit of plumbing)
[10:08:50] <kfunk> it'd probably be wise to add a NO_DBUS compile option, then inherit from that, otherwise inherit from QApplication
[10:09:12] <kfunk> (b/c I don't want to break the session-opening features on Linux)

PS: Make sure we can still start a separate KDevelop session!

arrowd added a subscriber: arrowd.Apr 12 2016, 1:47 PM

What needs to be done for this next?

kfunk added a comment.Apr 12 2016, 2:03 PM

I think we should strip dbus-daemon from the KDevelop installer package.

arrowd closed this task as Resolved.Apr 21 2016, 5:17 PM
arrowd claimed this task.