${libdir} usage

${libdir} usage

[JC]

Hi,

I'm currently putting together a bunch of recipes to install some cpan 
modules. I had some complaints by bitbake about files being installed 
but not shipped.

I figured that I need to populate FILES_{PN} but I'm not clear about 
what I should do with it: use ${libdir}, use "usr/*" ? Knowing that my 
image(s) directories mostly contain usr/lib/perl/* and sometimes usr/bin/*

What's the best practice ? That'll save me some time when I send the 
patch :)

Thanks for your help
Jay

Re: ${libdir} usage

[Paul Eggleton]

Hi Jay,

On Wednesday 02 October 2013 00:02:11 JC wrote:
> I'm currently putting together a bunch of recipes to install some cpan
> modules. I had some complaints by bitbake about files being installed
> but not shipped.
> 
> I figured that I need to populate FILES_{PN} but I'm not clear about
> what I should do with it: use ${libdir}, use "usr/*" ? Knowing that my
> image(s) directories mostly contain usr/lib/perl/* and sometimes usr/bin/*

Ultimately it depends on how those files have ended up there. If files have been 
installed in in /usr/lib because they've been installed in ${libdir} (this is 
the default for all autotooled recipes), then you should also use ${libdir} to 
match in FILES in case that value changes - some distros do this to flatten out 
/usr altogether for example.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: ${libdir} usage

[Jean-Charles JC Verdié]

On 10Oct 2013, at 12:01 PM, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:

> Hi Jay,
> 
> On Wednesday 02 October 2013 00:02:11 JC wrote:
>> I'm currently putting together a bunch of recipes to install some cpan
>> modules. I had some complaints by bitbake about files being installed
>> but not shipped.
>> 
>> I figured that I need to populate FILES_{PN} but I'm not clear about
>> what I should do with it: use ${libdir}, use "usr/*" ? Knowing that my
>> image(s) directories mostly contain usr/lib/perl/* and sometimes usr/bin/*
> 
> Ultimately it depends on how those files have ended up there. If files have been 
> installed in in /usr/lib because they've been installed in ${libdir} (this is 
> the default for all autotooled recipes), then you should also use ${libdir} to 
> match in FILES in case that value changes - some distros do this to flatten out 
> /usr altogether for example.
> 

Thanks !

Actually, I made a mistake and need to install those pm files in /lib not /usr/lib. cpan (instead of cpan-build) did everything ok :)

Regards
Jay

> Cheers,
> Paul
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre