<br><div class="gmail_quote">On Tue, Aug 14, 2012 at 3:50 PM, Koen Kooi <span dir="ltr"><<a href="mailto:koen@dominion.thruhere.net" target="_blank">koen@dominion.thruhere.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Op 14 aug. 2012, om 13:57 heeft Saul Wold <<a href="mailto:sgw@linux.intel.com">sgw@linux.intel.com</a>> het volgende geschreven:<br>
<div class="im"><br>
> On 08/14/2012 02:11 PM, Andrei Gherzan wrote:<br>
>> In the process of updating dbus, tests (in my opinion) are mandatory.<br>
>><br>
>> While compiling dbus with tests, dbus and dbus-glib are needed. To<br>
>> compile dbus-glib, dbus is needed (obviously). The only solution (to<br>
>> compile dbus with tests) that i found is to create a new recipe named<br>
>> dbus-tests where to compile dbus with --enable-tests<br>
>> --enable-embedded-tests, skip write to sysroot (noexec) and just package<br>
>> dbus-tests.<br>
>><br>
>> 1. Do you guys know a better solution for this?<br>
><br>
> We have started to think/chat about this, there was another patch on the list recently that Mark Hatle and I talked about tests.<br>
><br>
> I think having the tests enabled with DISTRO_FEATURE would allow for the flexibility of enabling then without always incurring the cost /overhead of longer compile times.<br>
><br>
> Can you incorporate the changes to the core recipe with out having to add a new dbus-tests recipe if you use DISTRO_FEATURE?<br>
><br></div></blockquote><div><br></div><div>As Koen as said in another mail i don't think there is another option than creating another recipe and we could add RDEPENDS to dbus if DISTRO_FEATURE contains dbus-tests.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
><br>
>> 2. What would be a good path to use for installing tests?<br>
> Same here, disucssion started.I would like to see tests go into ${datadir}/${BPN} (/usr/share/${BPN}<br>
<br>
</div>$datadir is not for executables, but for data<br>
<div class="im"><br></div></blockquote><div><br></div><div>Binaries and scripts?</div><div><br></div><div>ag</div></div>