Hi,

I am having a bit of trouble understanding something about
packaging.

I have a custom recipe to build a package that contains both
a daemon executable and a shared object interface library
for the daemon.

But the .so is only packaged in ${PN}-dev, not ${PN}, so
it doesn't end up on the target.

Is that expected behavior? How do I get my .so onto the target?

I worked around it by explicitly creating an extra package
and using FILES_${PN}-whatever to force the .so into it, but
now the .so doesn't get included in ${PN}-dev any more.

In general, is there a way to have a file included in two RPMs?
Or am I approaching this from the wrong direction?

Regards,
MV
-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to