On 08/14/2012 03:49 PM, Koen Kooi wrote:

Op 14 aug. 2012, om 13:11 heeft Andrei Gherzan <[email protected]> het volgende 
geschreven:

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?

It's actually the only solution that would work :)

2. What would be a good path to use for installing tests?

$bindir or $libexecdir IMO

Not bindir please!  Tests should live separate,

If it;s going to be libexecdir, really should be $libdir/$BPN as we want to move way from having things live in /usr/libexec, and yes with time $libexecdir will be $prefix/lib/$BPN.

Sau!


_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core



_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to