From: Philip Balister <philip@balister.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Package Updates
Date: Tue, 29 May 2012 08:10:48 -0400 [thread overview]
Message-ID: <4FC4BCC8.7090503@balister.org> (raw)
In-Reply-To: <CAK18fxFNrZPCZK2Ny6vr2qz6oHDFvtAA4Jw9SjjAb0djcxN7SQ@mail.gmail.com>
On 05/28/2012 09:58 AM, Andrei Gherzan wrote:
> On Mon, May 28, 2012 at 4:44 PM, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
>
>> On Mon, 2012-05-28 at 14:30 +0100, Burton, Ross wrote:
>>> On 28 May 2012 14:26, Andrei Gherzan <andrei@gherzan.ro> wrote:
>>>> There is an internal test suite for dbus. You can enable building those
>>>> tests in configure:
>>>> "--enable-tests"
>>>
>>> Is there a good reason why these shouldn't be always ran when building
>> dbus?
>>
>> Well, we're cross compiling so it depends how they're written and
>> whether they can run in a cross environment. We've also taken steps to
>> reduce our build time so if these need something like perl or python,
>> adding those into the dependency chain is problematic.
>>
>>
> 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.
Can you build the tests and package them separately? Then they could be
installed as part of a test image.
Philip
next prev parent reply other threads:[~2012-05-29 12:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 10:55 [PATCH 0/3] Package Updates Burton, Ross
2012-05-28 11:21 ` Radu Moisan
2012-05-28 11:21 ` Andrei Gherzan
2012-05-28 12:07 ` Paul Eggleton
2012-05-28 13:24 ` Radu Moisan
2012-05-28 13:26 ` Andrei Gherzan
2012-05-28 13:30 ` Burton, Ross
2012-05-28 13:44 ` Richard Purdie
2012-05-28 13:47 ` Burton, Ross
2012-05-28 13:58 ` Andrei Gherzan
2012-05-29 12:10 ` Philip Balister [this message]
2012-05-29 14:04 ` Radu Moisan
2012-05-29 8:29 ` dbus test suite Radu Moisan
2012-05-29 9:23 ` Radu Moisan
2012-05-29 9:28 ` Andrei Gherzan
2012-05-29 9:41 ` Radu Moisan
2012-05-29 9:42 ` Florin Sarbu
2012-05-29 11:18 ` Radu Moisan
2012-05-29 6:28 ` [PATCH 0/3] Package Updates Radu Moisan
2012-05-29 6:58 ` Radu Moisan
-- strict thread matches above, loose matches on Subject: below --
2014-03-10 3:48 Saul Wold
2013-12-10 19:16 Saul Wold
2013-08-05 21:07 Saul Wold
2013-07-23 23:53 Saul Wold
2012-05-29 7:01 Sarbu, Florin-Ionut (Florin)
2012-05-29 7:25 ` Radu Moisan
2012-05-25 8:50 Radu Moisan
2012-05-25 9:52 ` Koen Kooi
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=4FC4BCC8.7090503@balister.org \
--to=philip@balister.org \
--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.