From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: yocto@lists.yoctoproject.org, ycnakajsph@gmail.com
Subject: Re: [yocto][meta-openembedded] How to properly build a lib package
Date: Wed, 7 Aug 2024 12:21:14 +0300 [thread overview]
Message-ID: <ZrM8ikxC3AwTgDHR@nuoska> (raw)
In-Reply-To: <CAC3TgA+HFgXcckqxUVgUQsRfJySytZSAj3PtSRD6TLzT5_yDqg@mail.gmail.com>
Hi,
On Wed, Aug 07, 2024 at 10:47:57AM +0200, Yann CARDAILLAC via lists.yoctoproject.org wrote:
> Hi all,
>
> I'm working on upgrading different yocto BSPs to scarthgap, I'm having an
> error that I haven't seen. It's the one described here on stack overflow by
> someone else:
>
> https://stackoverflow.com/questions/64984897/yocto-package-requires-shared-library-but-no-providers-found-in-rdepends
>
> I have a very simple C library package that provides a shared library.
>
> My package is looking very close to:
> meta-openembedded/meta-oe/recipes-extended/p7zip/p7zip_16.02.bb
> <https://github.com/openembedded/meta-openembedded/blob/master/meta-oe/recipes-extended/p7zip/p7zip_16.02.bb>
>
> I don't really understand why we need to add the lib7z.so()(64bit)? Is
> there a "proper" way of avoiding that as it's not so common in other libs?
>
> I'm also not comfortable adding :
> INSANE_SKIP:${PN} += "dev-so"
>
> If any, can you point me to a simple library build that doesn't require the
> (64bit) that I don't really understand nor the INSANE_SKIP ? To sum up my
> need is to have a simple recipe for a shared library.
Please set soname correctly, see
https://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html
Shared libraries without soname are bad and this test correctly finds them.
Cheers,
-Mikko
next prev parent reply other threads:[~2024-08-07 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 8:47 [yocto][meta-openembedded] How to properly build a lib package Yann CARDAILLAC Pro
2024-08-07 9:12 ` Alexander Kanavin
2024-08-07 9:21 ` Mikko Rapeli [this message]
2024-08-07 13:13 ` Yann CARDAILLAC Pro
2024-08-07 13:19 ` Mikko Rapeli
2024-08-07 14:14 ` Yann CARDAILLAC Pro
2024-08-07 14:20 ` Mikko Rapeli
2024-08-28 9:50 ` Yann CARDAILLAC Pro
2024-08-29 7:34 ` Mikko Rapeli
2024-09-04 8:55 ` Ola x Nilsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZrM8ikxC3AwTgDHR@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=ycnakajsph@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.