On 05/29/2012 03:10 PM, Philip Balister wrote:
> On 05/28/2012 09:58 AM, Andrei Gherzan wrote:
>> On Mon, May 28, 2012 at 4:44 PM, Richard Purdie<
>> richard.purdie@linuxfoundation.org>  wrote:
>>
>>> On Mon, 2012-05-28 at 14:30 +0100, Burton, Ross wrote:
>>>> On 28 May 2012 14:26, Andrei Gherzan<andrei@gherzan.ro>  wrote:
>>>>> There is an internal test suite for dbus. You can enable building those
>>>>> tests in configure:
>>>>> "--enable-tests"
>>>> Is there a good reason why these shouldn't be always ran when building
>>> dbus?
>>>
>>> Well, we're cross compiling so it depends how they're written and
>>> whether they can run in a cross environment. We've also taken steps to
>>> reduce our build time so if these need something like perl or python,
>>> adding those into the dependency chain is problematic.
>>>
>>>
>> The fact that these tests are not compiled by default it's good. As a
>> normal user of dbus i don't need those. But while doing an update a compile
>> with tests i think it's necessary.
> Can you build the tests and package them separately? Then they could be
> installed as part of a test image.
>
> Philip
>
That would certainly be an option, but I really don't know where to 
start from :)
Meanwhile, I tried to further debug my scenario with 
--enable-modular-tests and I tried to manually resolve the missing *.h 
files (by copying them from dbus-glib to dbus include folder) just to 
see where is goes. I found out, somehow expected, that further undefined 
reference errors were thrown (to functions from dbus-glib). Thus now I'm 
looking to point somehow dbus tests to link against dbus-glib. Does 
anyone have a clue where should I look?

Radu