Package with both daemon and shared object

Package with both daemon and shared object

[Vuille, Martin (Martin)]

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 3114 bytes --]

Re: Package with both daemon and shared object

[Khem Raj]

[-- Attachment #1.1: Type: text/plain, Size: 1416 bytes --]


> On Oct 14, 2015, at 9:25 AM, Vuille, Martin (Martin) <vmartin@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@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>

[-- Attachment #1.2: Type: text/html, Size: 9338 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

Re: Package with both daemon and shared object

[Vuille, Martin (Martin)]

> From: Khem Raj [mailto:raj.khem@gmail.com] 
> Sent: October 14, 2015 1:25 PM
> 
> 
> > On Oct 14, 2015, at 9:25 AM, Vuille, Martin (Martin) <vmartin@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

Thanks! I knew about this at some point but it completely slipped my mind.

Problem fixed now
MV