dbus library search rules for qdbus
Ralf Habacker
ralf.habacker at freenet.de
Tue Jul 15 12:39:18 CEST 2008
Hi,
Recent dbus cmake build system (and binary packages) uses different dll
names for release/debug build (dbus-1/dbus1d) and compiler (mingw:
libdbus-1(d).dll msvc: dbus-1(d).dll)
While linking the dbus libraries to the qdbus module using the import
libraries (which is indicated by the QT_LINKED_LIBDBUS macro) qt honors
all the above mentioned dll naming scheme.
In the opposite the newly added qdbus feature to load the dbus library
dynamically breaks debug support because qdbus only loads dbus-1.dll
(the msvc release dll) regardless of compiler and compile mode.
Unfortunally this makes it impossible to debug qdbus with dbus. The
appended patch fixes this problem according to the following rules:
/*
dbus library searching rules as already implemented for
linked qdbus (with extension [1],[2])
os compiler compile type library
versions library name
win32 gcc debug
--- libdbus-1d, libdbus-1[1], dbus-1[2]
win32 gcc release
--- libdbus-1, dbus-1 [2]
win32 msvc debug
--- dbus-1d, dbus-1[1]
win32 msvc release
--- dbus-1
unix gcc
debug 3,2 dbus-1
unix gcc
release 3,2 dbus-1
[1] when qdbus is compiled as debug release and there is
no dbus debug library, the dbus release library will be taken
[2] when no gcc debug or release dbus library is
available a msvc dbus release build will be taken.
*/
Does anyone see a problem with this rules ?
Ralf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qt-dbus-libname.diff
Type: text/x-diff
Size: 2535 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-windows/attachments/20080715/83a6f5c6/attachment.bin
More information about the Kde-windows
mailing list