* ${libdir} usage
@ 2013-10-01 22:02 JC
2013-10-10 10:01 ` Paul Eggleton
0 siblings, 1 reply; 3+ messages in thread
From: JC @ 2013-10-01 22:02 UTC (permalink / raw)
To: yocto@yoctoproject.org
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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: ${libdir} usage
2013-10-01 22:02 ${libdir} usage JC
@ 2013-10-10 10:01 ` Paul Eggleton
2013-10-10 13:22 ` Jean-Charles JC Verdié
0 siblings, 1 reply; 3+ messages in thread
From: Paul Eggleton @ 2013-10-10 10:01 UTC (permalink / raw)
To: JC; +Cc: yocto
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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: ${libdir} usage
2013-10-10 10:01 ` Paul Eggleton
@ 2013-10-10 13:22 ` Jean-Charles JC Verdié
0 siblings, 0 replies; 3+ messages in thread
From: Jean-Charles JC Verdié @ 2013-10-10 13:22 UTC (permalink / raw)
To: Paul Eggleton; +Cc: yocto
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-10-10 13:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-01 22:02 ${libdir} usage JC
2013-10-10 10:01 ` Paul Eggleton
2013-10-10 13:22 ` Jean-Charles JC Verdié
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.