[Mingw-cross-env-list] About the DBUS package

[René Berber]

Hello again,

I just tested a Qt application that uses DBUS, this application I have
been building with my own build of DBUS so the main change is that now
I'm using the one with the cross-development environment, plus Qt has
been rebuild, here the difference is that I used to build Qt with the
configure parameter -dbus, the new qt.mk file uses -dbus-linked (and
this is actually what I wanted to test).

There are 2 differences, and a problem in the result:

 * The problem: the application (statically linked) still depends on the
dynamic library, which is not produced by dbus.mk.

 * Diff.1: my Qt build produces a dependency to dbus-1.dll, the new Qt
build produces one to libdbus-1-3.dll;

 * Diff.2: with my Qt build the library doesn't show as a dynamic
dependency, with the new one it does (so its better).

Of course the only important point is the problem, the library is not
build and/or not installed.

The use of the non-static library was not intended, so that is another
problem, but as I commented on an earlier message, I think this is the
way Qt is "designed", it never uses the static library.  I'm not using
anything explicit on Qt to pull static or dynamic libraries, its as
simple as (application.pro):

CONFIG += qt qdbus thread debug link_pkgconfig
PKGCONFIG = fontconfig libcurl openssl dbus-1 libevent
win32:DEFINES += QT_DBUS

The only possible suspect is usr/i686-pc-mingw32/lib/pkgconfig/dbus-1.pc
which was changed when I make(d) dbus, actually I just noticed that it
is a newer version than the one I was using last, and the relevant part
doesn't have anything to change the type of library:

Version: 1.4.1
Libs: -L${libdir} -ldbus-1  -lws2_32
Cflags: -I${includedir}/dbus-1.0 -I${libdir}/dbus-1.0/include

-- 
René Berber