[OE-core] dbus with tests

Andrei Gherzan andrei at gherzan.ro
Tue Aug 14 14:58:33 UTC 2012


On Tue, Aug 14, 2012 at 3:50 PM, Koen Kooi <koen at dominion.thruhere.net>wrote:

>
> Op 14 aug. 2012, om 13:57 heeft Saul Wold <sgw at linux.intel.com> het
> volgende geschreven:
>
> > On 08/14/2012 02:11 PM, Andrei Gherzan wrote:
> >> In the process of updating dbus, tests (in my opinion) are mandatory.
> >>
> >> While compiling dbus with tests, dbus and dbus-glib are needed. To
> >> compile dbus-glib, dbus is needed (obviously). The only solution (to
> >> compile dbus with tests) that i found is to create a new recipe named
> >> dbus-tests where to compile dbus with --enable-tests
> >> --enable-embedded-tests, skip write to sysroot (noexec) and just package
> >> dbus-tests.
> >>
> >> 1. Do you guys know a better solution for this?
> >
> > We have started to think/chat about this, there was another patch on the
> list recently that Mark Hatle and I talked about tests.
> >
> > 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.
> >
> > Can you incorporate the changes to the core recipe with out having to
> add a new dbus-tests recipe if you use DISTRO_FEATURE?
> >
>

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.


> >
> >> 2. What would be a good path to use for installing tests?
> > Same here, disucssion started.I would like to see tests go into
> ${datadir}/${BPN} (/usr/share/${BPN}
>
> $datadir is not for executables, but for data
>
>
Binaries and scripts?

ag
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20120814/6b5ae920/attachment-0002.html>


More information about the Openembedded-core mailing list