[oe] 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 at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>