Re: [PATCH 0/3] Package Updates

[Radu Moisan <radu.moisan@intel.com>]

[-- Attachment #1: Type: text/plain, Size: 1876 bytes --]

this is what I was looking for. I'll try it soon as my "hard-codded" 
version finshes buiding. thanks.

Radu

On 05/29/2012 10:01 AM, Sarbu, Florin-Ionut (Florin) wrote:
> EXTRA_OECONF+="--enable-tests" may be what you are looking for.
>
> -----Original Message-----
> *From: *Radu Moisan [radu.moisan@intel.com <mailto:radu.moisan@intel.com>]
> *Sent: *Monday, May 28, 2012 11:24 PM Pacific Standard Time
> *To: *openembedded-core@lists.openembedded.org
> *Subject: *Re: [OE-core] [PATCH 0/3] Package Updates
>
>
>
> 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

[-- Attachment #2: Type: text/html, Size: 3609 bytes --]