7b6ab50c68
This allows the tests to be run on Windows too by using TCP socket connections instead of requiring Unix sockets. The tests shouldn't have hardcoded the path, which came from QDBusServer anyway. Now the tests simply defer to QDBusServer. This is a slight behavior change for Windows, but not one that should matter since anyone who was using the default constructor resulted in a QDBusServer that failed to listen. [ChangeLog][QtDBus][QDBusServer] Fixed a bug that made QDBusServer's default constructor try to bind to a Unix socket on non-Unix systems. Now QDBusServer will attempt to bind to a TCP socket instead. Change-Id: I2a126019671c2d90257e739ed3aff7938d1fe946 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@theqtcompany.com> Reviewed-by: Simon Hausmann <simon.hausmann@digia.com> |
||
|---|---|---|
| .. | ||
| qdbusabstractadaptor | ||
| qdbusabstractinterface | ||
| qdbusconnection | ||
| qdbusconnection_no_bus | ||
| qdbuscontext | ||
| qdbusinterface | ||
| qdbuslocalcalls | ||
| qdbusmarshall | ||
| qdbusmetaobject | ||
| qdbusmetatype | ||
| qdbuspendingcall | ||
| qdbuspendingreply | ||
| qdbusreply | ||
| qdbusservicewatcher | ||
| qdbusthreading | ||
| qdbustype | ||
| qdbusxmlparser | ||
| dbus.pro | ||