From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Andrei Gherzan <andrei@gherzan.ro>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: dbus with tests
Date: Tue, 14 Aug 2012 19:24:16 +0300 [thread overview]
Message-ID: <502A7BB0.4050708@linux.intel.com> (raw)
In-Reply-To: <1EE0C4BA-A5E0-42FC-B354-89B29C5C6C22@dominion.thruhere.net>
On 08/14/2012 03:49 PM, Koen Kooi wrote:
>
> Op 14 aug. 2012, om 13:11 heeft Andrei Gherzan <andrei@gherzan.ro> 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
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2012-08-14 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 11:11 dbus with tests Andrei Gherzan
2012-08-14 11:57 ` Saul Wold
2012-08-14 12:50 ` Koen Kooi
2012-08-14 14:58 ` Andrei Gherzan
2012-08-14 12:49 ` Koen Kooi
2012-08-14 16:24 ` Saul Wold [this message]
2012-08-14 16:53 ` Koen Kooi
2012-08-14 17:01 ` Burton, Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=502A7BB0.4050708@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=andrei@gherzan.ro \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.