From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
To: jguittet.opensource@witekio.com, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Implicit RPROVIDES somewhere ?
Date: Wed, 17 Apr 2024 10:32:50 +0200 [thread overview]
Message-ID: <0b73263e-6a9d-4c89-be79-b3644c9e02a9@theobroma-systems.com> (raw)
In-Reply-To: <22839.1713287385608688409@lists.yoctoproject.org>
Hi Joel,
On 4/16/24 19:09, Joel GUITTET via Lists.Yoctoproject.Org wrote:
> You don't often get email from jguittet.opensource=witekio.com@lists.yoctoproject.org. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
> Hello Quentin,
>
> Thanks for the quick reply on this question!
>
> The reason of this organisation is that my customer is responsible of providing library "bar" (he cannot share the source code with me), and we are responsible of providing library "foo". It's not confortable for sure, but it's the actual state. So my customer provides me the "bar" libraries (arm and aarch64) compiled (so files), that I copy/paste in my layer. And then I build "foo" libraries that are linked to "bar" and additionally I have to install only the "foo" libraries in the rootfs.
>
So far so good. Not an uncommon setup, bar recipe would be following the
prebuilt binary section in the documentation.
https://docs.yoctoproject.org/dev-manual/prebuilt-libraries.html
The thing I do not understand is why you do NOT want bar on the rootfs?
Your foo shared library explicitly states that it requires libbar.so to
be able to run, why do you not want libbar.so in your rootfs?
> The library that is building "foo" have nothing specific to the architecture. The IMAGE_INSTALL has "lib32-foo" and "foo".
> But something to mention that may have an impact here : because of this organization above my recipe that is building "foo" have the following (else I don't succeed to build):
This smells like bad build system/instructions for the foo recipe. All
libraries built by Yocto should be versioned, I highly recommend to fix
your foo SW to have some version in there to not have to deal with this.
It's best practice and will help you in the long run anyway (actually
trying to figure out which version the customer is using by simply
looking at the filename for example). But I don't think that should
impact libfoo being added or not.
>
> FILES_SOLIBSDEV = ""
> INSANE_SKIP:${PN} += "dev-so"
> INSANE_SKIP:${PN} += "file-rdeps"
>
This INSANE_SKIP isn't that common and I don't think it's that good of
an idea?
There's one thing I missed is that you're building with multilib. Do you
actually have a lib32-bar package and a bar package? Is your libbar.so
available in both aarch32 and aarch64 architectures?
I assume that the automagic RDEPENDS got broken for lib32-foo and you
are not seeing it because of
INSANE_SKIP:${PN} += "file-rdeps"
It's probably trying to locate a multilib lib32 package containing
libbar.so but cannot find any and complains about it. The aarch64
package does find a package for libbar.so so it adds it automatically.
Cheers,
Quentin
next prev parent reply other threads:[~2024-04-17 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 14:50 Implicit RPROVIDES somewhere ? Joel GUITTET
2024-04-16 15:14 ` [yocto] " Quentin Schulz
2024-04-16 17:09 ` Joel GUITTET
2024-04-17 8:32 ` Quentin Schulz [this message]
2024-04-18 8:50 ` Joel GUITTET
2024-04-18 9:13 ` Quentin Schulz
2024-04-18 10:11 ` Joel GUITTET
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=0b73263e-6a9d-4c89-be79-b3644c9e02a9@theobroma-systems.com \
--to=quentin.schulz@theobroma-systems.com \
--cc=jguittet.opensource@witekio.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.