evince: who is responsible to pack all within usr/lib/evince/3/backends to ${PN}?

evince: who is responsible to pack all within usr/lib/evince/3/backends to ${PN}?

[Andreas Müller]

Since the staticdev update of insane.bbclass in oe-core I get

WARNING: QA Issue: non -staticdev package contains static .a library:
evince path '/work/armv7a-angstrom-linux-gnueabi/evince-2.32.0-r1/packages-split/evince/usr/lib/evince/3/backends/libtiffdocument.a'
WARNING: QA Issue: non -staticdev package contains static .a library:
evince path '/work/armv7a-angstrom-linux-gnueabi/evince-2.32.0-r1/packages-split/evince/usr/lib/evince/3/backends/libpixbufdocument.a'
WARNING: QA Issue: non -staticdev package contains static .a library:
evince path '/work/armv7a-angstrom-linux-gnueabi/evince-2.32.0-r1/packages-split/evince/usr/lib/evince/3/backends/libcomicsdocument.a'
WARNING: QA Issue: non -staticdev package contains static .a library:
evince path '/work/armv7a-angstrom-linux-gnueabi/evince-2.32.0-r1/packages-split/evince/usr/lib/evince/3/backends/libpdfdocument.a'

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}?

Regards

Andreas

Re: evince: who is responsible to pack all within usr/lib/evince/3/backends to ${PN}?

[Saul Wold]

On 01/26/2012 05:16 PM, Andreas Müller wrote:
> Since the staticdev update of insane.bbclass in oe-core I get
>
> WARNING: QA Issue: non -staticdev package contains static .a library:
> evince path '/work/armv7a-angstrom-linux-gnueabi/evince-2.32.0-r1/packages-split/evince/usr/lib/evince/3/backends/libtiffdocument.a'
> WARNING: QA Issue: non -staticdev package contains static .a library:
> evince path '/work/armv7a-angstrom-linux-gnueabi/evince-2.32.0-r1/packages-split/evince/usr/lib/evince/3/backends/libpixbufdocument.a'
> WARNING: QA Issue: non -staticdev package contains static .a library:
> evince path '/work/armv7a-angstrom-linux-gnueabi/evince-2.32.0-r1/packages-split/evince/usr/lib/evince/3/backends/libcomicsdocument.a'
> WARNING: QA Issue: non -staticdev package contains static .a library:
> evince path '/work/armv7a-angstrom-linux-gnueabi/evince-2.32.0-r1/packages-split/evince/usr/lib/evince/3/backends/libpdfdocument.a'
>
> 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.

Sau!

> Regards
>
> Andreas
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: evince: who is responsible to pack all within usr/lib/evince/3/backends to ${PN}?

[Andreas Müller]

On Fri, Jan 27, 2012 at 9:43 AM, Andreas Müller
<schnitzeltony@googlemail.com> wrote:
> On Fri, Jan 27, 2012 at 2:28 AM, Saul Wold <sgw@linux.intel.com> 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

Re: [OE-core] evince: who is responsible to pack all within usr/lib/evince/3/backends to ${PN}?

[Saul Wold]

On 01/27/2012 04:48 AM, Andreas Müller wrote:
> On Fri, Jan 27, 2012 at 9:43 AM, Andreas Müller
> <schnitzeltony@googlemail.com>  wrote:
>> On Fri, Jan 27, 2012 at 2:28 AM, Saul Wold<sgw@linux.intel.com>  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.
>
Actually the ordering of PACKAGES matters here and since bitbake.conf 
lists the ${PN}-dev and ${PN}-staticdev package before ${PN}, you can 
append the ${libdir}/${BPN}/3/backends/*.a to FILES_${PN}-staticdev and 
it will pull those first before doing the FILES_${PN}. does that make 
sense?  You don't have to re-write FILES_${PN}.

Sau!

> Andreas
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>