From: "Jeremy A. Puhlman" <jpuhlman@mvista.com>
To: Rail Shafigulin <rail@esenciatech.com>, yocto@yoctoproject.org
Subject: Re: executable depends on the library that is built in the same recipe
Date: Mon, 11 Dec 2017 11:54:17 -0800 [thread overview]
Message-ID: <fffb74b4-80b5-60fb-0b4b-71878e29a622@mvista.com> (raw)
In-Reply-To: <CAOLNbFanXur1zRF7KtVpdN4n6Pyx5JW7P2xhfc+74UmTabyicA@mail.gmail.com>
Given it is looking for libMyTool.so and not a versioned library, my
guess is that the shared
library is not setting a proper soname when being built. All libraries
should be built with a soname,
and if done correctly should be versioned. The .so file generally
shouldn't be the runtime library
but a link back to the versioned library, so you get something that
looks like:
/usr/lib/libz.so -> libz.zo.1.2.11
/usr/lib/libz.so.1.2.11
/usr/lib/libz.so.1 -> libz.so.1
On 12/11/2017 11:45 AM, Rail Shafigulin wrote:
> I have a recipe that builds a library and an executable. Executable
> depends on the library which built int he same recipe. When I run
> bitbake I get the following error:
>
> WARNING: mytool-1.0+gitAUTOINC+3e2b76e330-r0 do_package_qa: QA Issue:
> /bin/mytool contained in package mytool requires libMyTool.so, but no
> providers found in RDEPENDS_mytool? [file-rdeps]
>
> I tried the suggestion given by the bitbake putting mytool in
> REDEPNDS_${PN}, but that didn't work. I also tried looking online for
> the solution but didn't find one.
>
> Can someone help out?
>
>
--
Jeremy A. Puhlman
jpuhlman@mvista.com
next prev parent reply other threads:[~2017-12-11 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 19:45 executable depends on the library that is built in the same recipe Rail Shafigulin
2017-12-11 19:54 ` Jeremy A. Puhlman [this message]
2017-12-12 4:18 ` Vineeth Karumanchi
2017-12-12 19:14 ` Rail Shafigulin
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=fffb74b4-80b5-60fb-0b4b-71878e29a622@mvista.com \
--to=jpuhlman@mvista.com \
--cc=rail@esenciatech.com \
--cc=yocto@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.