<br>Hey,<br><br><div class="gmail_quote">On Mon, Feb 28, 2011 at 4:59 PM, Romain Pokrzywka <span dir="ltr"><<a href="mailto:romain.pokrzywka@kdab.com">romain.pokrzywka@kdab.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Vincent,<br>
<br>
If you just want to make sure the bus starts up correctly, you can open a console and go to the bin folder where dbus<br>
was build, then try running:<br></blockquote><div><br>they are in my PATH.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
dbus-daemon.exe --session<br></blockquote><div><br>done<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
which starts up the bus, then :<br>
<br>
dbus-monitor<br>
<br>
It should print out some info, that means your bus is up and running, and ready to register services objects.<br></blockquote><div><br>actually, no. I have:<br><br>$ dbus-monitor.exe<br>Failed to open connection to session bus: Failed to get autolaunch address from launched dbus-daemon<br>
<br>in the Task manager, I see one dbus-daemon launch by dbus-daemon.exe --session. Then when i launch bus-monitor.exe, I see 2 others dbus-daemon.exe processes, one terminated almost immediatly (so it remains 2 dbus-daemon.exe processes running).<br>
<br>That's all I can say.<br><br>Vincent<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div class="h5"><br>
<br>
On Sunday 27 February 2011 16:38:17 Vincent Torri wrote:<br>
> Hey,<br>
><br>
> first, I know almost nothing about dbus :-)<br>
><br>
> I have compiled dbus on Windows (Windows XP, using MinGW) and I would like<br>
> to see if it works. I have read most of the pages on the site, I have read<br>
> the README, but always without precise indications. What I would like to<br>
> have is something like:<br>
><br>
> * launch that command<br>
> * launch another command<br>
> * you should have in your terminal that message<br>
><br>
> If I have missed some info (specific to Windows), please tell me. If not,<br>
> that kind of documentation should go in the "Windows port" section, imho<br>
><br>
> thank you<br>
><br>
> Vincent Torri<br>
<br>
<br>
</div></div><br>_______________________________________________<br>
dbus mailing list<br>
<a href="mailto:dbus@lists.freedesktop.org">dbus@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/dbus" target="_blank">http://lists.freedesktop.org/mailman/listinfo/dbus</a><br>
<br></blockquote></div><br>