Build changes for 0.61

Diane Holt Diane.Holt at
Wed May 24 19:38:08 PDT 2006

Hi John,

Thanks for the quick reply. But I'm not sure I fully understand it. Are
you saying nothing currently actually needs the .xml file? Can I simply
modify my tools/ to not list it in the dependencies for
dbus-glib-bindings.h (and take the dbus-bus-introspect.xml target out)?
Will dbus-glib-bindings.h still get built correctly if I do?

The reason I'm wanting to not have the launch/send get done is because
I'm trying to build dbus for ARM, in a Scratchbox environment, and while
it works for the x86 build, it doesn't for the ARM. Not sure why it
fails -- the daemon launches -- I can see it in my process table, but
the connection fails, maybe due to the daemon actually running via the
qemu-arm emulation? I was just going to source-control the .xml file and
remove the target for it -- but if I can simply remove the dependency
altogether, even better.


-----Original Message-----
From: John (J5) Palmieri [mailto:johnp at] 
Sent: Wednesday, May 24, 2006 6:10 PM
To: Diane Holt
Cc: dbus at
Subject: Re: Build changes for 0.61

Hello diane,

dbus-bus-introspect.xml is just a stub file for the glib bindings.  From
it we generate bindings to the bus methods such as AquireName and
ListNames, etc.  In reality we could just do this at dist time or even
take it out altogether because the bindings just give an added layer of
convenience when talking to the bus.  I'm not sure anyone actually uses
them and if they did it is easy enough to move to pure dbus calls

On Wed, 2006-05-24 at 17:13 -0700, Diane Holt wrote:
> In the build process for 0.61, dbus is launched and a dbus-send is
> then done. It looks to be getting done for the generation of
> dbus-bus-introspect.xml, but I don't see what this file is actually
> used for - I don't see it getting installed anywhere. Is this file
> actually needed by something, and if so, is it something that's
> essential to the building of dbus, or can whatever needs it be
> disabled?

John (J5) Palmieri <johnp at>

More information about the dbus mailing list