<br>hey,<br><br><div class="gmail_quote">On Sat, Apr 9, 2011 at 3:40 AM, Mat <span dir="ltr"><<a href="mailto:matlinuxer2@gmail.com">matlinuxer2@gmail.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,<br>
<br>
as I know, the default env setting on windows is,<br>
<br>
"DBUS_SESSION_BUS_ADDRESS=autolaunch:scope=install-path"<br>
<br>
the "install-path" let dbus resolve the dbus session channel by "path<br>
of libdbus-1.dll", so "the file location of libdbus-1.dll" and "the<br>
search path order" will affect the connections between run-time<br>
processes.<br>
<br>
btw, in my previous test, dbus seems to check libdbus-1.dll's parent<br>
dir's name, and its related path "bin/libdbus-1.dll" ( parent dir name<br>
should be "bin" ), and ...etc/. So I suggest that preserver the<br>
original directory sturcture and put it on one of the system default<br>
search path.<br></blockquote><div><br>i did an<br><br>export DBUS_SESSION_BUS_ADDRESS=autolaunch:scope=install-path<br><br>but same problem. The installation is the same than on linux, except that DLL are in $prefix/bin instead of $prefix/lib. So i think that the directory structure is preserved<br>
<br>Vincent Torri<br></div></div>