From: Ola x Nilsson <ola.x.nilsson@axis.com>
To: <yocto@lists.yoctoproject.org>
Cc: <mikko.rapeli@linaro.org>
Subject: Re: [yocto][meta-openembedded] How to properly build a lib package
Date: Wed, 4 Sep 2024 10:55:37 +0200 [thread overview]
Message-ID: <jwqv7zbn6gm.fsf@axis.com> (raw)
In-Reply-To: <ZtAklNWwtgL0vbhQ@nuoska> (Mikko Rapeli's message of "Thu, 29 Aug 2024 10:34:44 +0300")
On Thu, Aug 29 2024, Mikko Rapeli wrote:
> Hi,
>
> On Wed, Aug 28, 2024 at 11:50:03AM +0200, Yann CARDAILLAC Pro wrote:
>> Hi Mikko,
>>
>> Well without the RPROVIDES I get the following error when a package DEPENDS
>> on it :
>>
>> ERROR: rj2d-com-1.1-r0 do_package_qa: QA Issue: /usr/bin/rj2d- com
>> contained in package rj2d- com requires librj2d.so()(64bit), but no
>> providers found in RDEPENDS:rj2d-com? [file-rdeps]
>>
>> The only solution I found was to add the RPROVIDES. Is there something I'm
>> doing wrong?
>>
>> Basically the rj2d-com package DEPENDS and RDEPENDS:${PN} to librj2d, and
>> without the RPROVIDES with librj2d.so()(64bit) I get errors.
>>
>> Is there something wrong with the approach ?
>
> I think bitbake should be auto-detecting the shared library RDEPENS. RPROVIDES
> is usually only set when there is a virtual provider which multiple recipes
> and binary package provide.
>
> Something doesn't feel right about this.
I think it is the missing soname mentioned earlier. It needs to be set
using a linker flag.
/Ola
prev parent reply other threads:[~2024-09-04 8:55 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
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 [this message]
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=jwqv7zbn6gm.fsf@axis.com \
--to=ola.x.nilsson@axis.com \
--cc=mikko.rapeli@linaro.org \
--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.