<div class="gmail_quote">On Mon, May 28, 2012 at 4:44 PM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Mon, 2012-05-28 at 14:30 +0100, Burton, Ross wrote:<br>
> On 28 May 2012 14:26, Andrei Gherzan <<a href="mailto:andrei@gherzan.ro">andrei@gherzan.ro</a>> wrote:<br>
> > There is an internal test suite for dbus. You can enable building those<br>
> > tests in configure:<br>
> > "--enable-tests"<br>
><br>
> Is there a good reason why these shouldn't be always ran when building dbus?<br>
<br>
</div>Well, we're cross compiling so it depends how they're written and<br>
whether they can run in a cross environment. We've also taken steps to<br>
reduce our build time so if these need something like perl or python,<br>
adding those into the dependency chain is problematic.<br>
<br></blockquote><div><br></div><div>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. </div>
<div> </div><div>@g</div></div>