On Fri, Jan 27, 2012 at 9:43 AM, Andreas Müller
<[email protected]> wrote:
> On Fri, Jan 27, 2012 at 2:28 AM, Saul Wold <[email protected]> wrote:
>> On 01/26/2012 05:16 PM, Andreas Müller wrote:
>>>
>>> I checked: the complete contents of /usr/lib/evince/3/backends go to
>>> evince package and I would like to move *.a to ${PN}-staticdev and
>>> *.la to ${PN}-dev but I don't understand: who is responsible for
>>> adding all this to ${PN}?
>>>
>> bitbake.conf defines where most files should go, but when you get files in
>> sub-directories, such as /usr/lib/evince/..., then the recipe needs to do a
>> little more work. If you look at the evince_2.32.0.bb, there already is a
>> FILES_${PN}-staticdev that adds some extensions, you need to add this set of
>> backends to that list, probably same with the .la to the -dev package.
>>
> Why I asked this: Maybe there is a chance to fix this more globally
> instead of one by one in each recipe. But therefore I need to know
> where the path is packed.
>
I looked around for this a bit: As Saul pointed out, in bitbake.conf we have
FILES_${PN} = ... ${libdir}/${BPN}/* ...
This
* drags in all below this directory ( e.g *.la / *.a )
* Forces me to rewrite FILES_${PN} in evince ( e.g just adding
${libdir}/${BPN}/*/backends/*.a to FILES_${PN}-staticdev fixes nothing
). This is something I would like to avoid.
Suggestions?
I guess others but evince are also affected.
Andreas
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
