[yocto] Package with both daemon and shared object

[Khem Raj]

> On Oct 14, 2015, at 9:25 AM, Vuille, Martin (Martin) <vmartin at avaya.com> wrote:
> 
> 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.

yes thats default and if the .so was built using proper .so versioning scheme.
.so is a symlink to .so.X.Y.Z


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

You should try to change building your .so to use versioning scheme.
it makes your packaging simple with OE and other places.

FILES_SOLIBSDEV = “${libdir}/*.so”
but thats not a preferred solution, its a workaround


> 
> 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 at yoctoproject.org <mailto:yocto at yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20151014/bffe6c99/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20151014/bffe6c99/attachment.pgp>