From: Radu Moisan <radu.moisan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Package Updates
Date: Tue, 29 May 2012 09:58:53 +0300 [thread overview]
Message-ID: <4FC473AD.6060100@intel.com> (raw)
In-Reply-To: <4FC46C84.5090408@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
On 05/29/2012 09:28 AM, Radu Moisan wrote:
>
>
> On 05/28/2012 04:26 PM, Andrei Gherzan wrote:
>> On Mon, May 28, 2012 at 4:24 PM, Radu Moisan <radu.moisan@intel.com
>> <mailto:radu.moisan@intel.com>> wrote:
>>
>> On 05/28/2012 02:21 PM, Andrei Gherzan wrote:
>>
>> Dbus comes with a test suite. Running those should be a must.
>>
>> I could not find how to run the test suite. I've tried
>> dbus-daemon, dbus-monitor, and the rest, but non of them have
>> options for some runtime checks. Other than that I imagine the
>> test suite you mention must come in a separate package. Do we
>> have a recipe for that to? Which image should I build to have
>> that package included and be able to test?
>>
>>
>> There is an internal test suite for dbus. You can enable building
>> those tests in configure:
>> "--enable-tests"
>>
>> @g
>>
> So, isn't there a way of specifying build options in some file that
> bitbake will use afterwards to do the build? For instance where from
> ./configure is executed (from within bitbake I assume). I tried to
> take a look over configure file of dbus but could not figure out a way
> of hardcoding the --enable-tests option (not that hardcoding would be
> a best choice, but for testing purposes I considered it a choice). Any
> info on this is much appreciated.
>
> Thanks,
> Radu
Found it in oe_runconf(). Will try to build them, see what comes out of
it :)
Any comments still apreciated.
Radu
[-- Attachment #2: Type: text/html, Size: 2946 bytes --]
next prev parent reply other threads:[~2012-05-29 7:03 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
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 [this message]
-- 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=4FC473AD.6060100@intel.com \
--to=radu.moisan@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox