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
Still not entirely sure what triggers the startup of dbus-daemon (it's not us, nor KF5).
Things to do:
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | None | T1354 KDevelop 5 on Windows PSA blockers | ||
Resolved | arrowd | T1339 Windows: Make sure we don't start/use dbus-daemon |
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!