[meta-freescale] [meta-fsl-arm][PATCH 4/4] libmcc: Add runtime dependency for kernel-module-mcc-dev

[Otavio Salvador]

On Tue, Jan 6, 2015 at 2:49 PM, Daiane Angolini <daiane.list at gmail.com> wrote:
> On Tue, Jan 6, 2015 at 2:30 PM, Otavio Salvador <otavio at ossystems.com.br> wrote:
>> The kernel-module-mcc-dev brings the kernel API headers used when
>> doing application development which uses the libmcc.
>
> In my point of view this commit log is confusing, but, because I
> haven´t understood it in fact I cannot propose something better.

I am open for suggestion here. Someone?

>> This improves the SDK support for Vybrid MCC application development.
>>
>> Change-Id: Icd8311c79a87500c0a9d97d9b63fb0340a5908a1
>> Signed-off-by: Otavio Salvador <otavio at ossystems.com.br>
>> ---
>>  recipes-bsp/libmcc/libmcc_1.05.bb | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/recipes-bsp/libmcc/libmcc_1.05.bb b/recipes-bsp/libmcc/libmcc_1.05.bb
>> index de5ec7f..82507a6 100644
>> --- a/recipes-bsp/libmcc/libmcc_1.05.bb
>> +++ b/recipes-bsp/libmcc/libmcc_1.05.bb
>> @@ -22,3 +22,5 @@ COMPATIBLE_MACHINE = "(vf60)"
>>  do_install() {
>>      oe_runmake 'DESTDIR=${D}' install
>>  }
>> +
>> +RDEPENDS_${PN}-dev += "kernel-module-mcc-dev"
>
> Let me understand. You are adding a RDEPENDS into the -dev package for
> the kernel-module-mmc-dev. Right? Well, we can handle this offline as
> well.

Yes. The libmcc-dev will being kernel-module-mcc-dev which has mcc_* headers.

> Another thing, you made 4 patches and you have included the error
> message in none commit log. Do you think the error message would be
> searched?

There's not much to search for. I am amazed no one has reported it
before as seems libmcc was not very useful without this :)

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750