D-Bus session bus

[Kevin Krammer]

Hi folks,

I had some difficulties today getting the D-Bus session bus setup right.

The base situation is like this:

KDE is built into C:\KDE\trunk using emerge
I am working on a "BitRock Install Builder" based installer for an application 
which uses Akonadi.
The installer puts Akonadi, the application and some Akonadi resources into a 
subdirectory in c:\Program Files.

When I run the application, it starts D-Bus and Akonadi (good), Akonadi starts 
the agents (it also finds the ones in C:\KDE\trunk\bin, but still ok).

However, each of those started from %KDEROOT% starts its own D-Bus and its own 
Akonadi!

Andreas hinted that I could try changing the D-Bus config to use tcp instead 
of autolaunch [1].
Doing that made the app start D-Bus but fail to detect that (dbus-daemon was 
shown running in the process monitor, but the app complained about it not 
finding the session bus).

I now got it working by commenting the patch apply setion in 
emerge/portage/win32libs-sources/dbus-src/dbus-src-1.3.1.py and using D-Bus 
config tcp with host and port.

Since hardcoding a port is quite likely a bad idea, any suggestions what I 
could try instead?

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-windows/attachments/20100825/38873184/attachment.sig