From: Paul Sokolovsky <pmiscml@gmail.com>
To: Rob Kramer <robk@starhub.net.sg>
Cc: openembedded-devel@openembedded.org,
openembedded-devel@lists.openembedded.org
Subject: Re: How to specify RDEPENDS properly?
Date: Thu, 22 Feb 2007 14:14:07 +0200 [thread overview]
Message-ID: <109483350.20070222141407@gmail.com> (raw)
In-Reply-To: <erjv1k$sm8$1@sea.gmane.org>
Hello Rob,
Thursday, February 22, 2007, 1:32:55 PM, you wrote:
> Hi all,
> I'm trying to build my custom image after updating OE (it worked several
> months back :). I've already converted several things to the new style, but
> I can't get my RDEPENDS right. There are about 4 problematic packages, but
> let's pick readline.
[]
> I don't really understand when to use the package name (readline), and when
> to use the ipk name (libreadline[4]). Several months back I had to RDEPEND
> on libreadline, so try that again:
First thing to understand is that OE deals with 2 distinct
namespaces: one is for recipes, another is for packages. Each recipes
may build one or more packages. Names of recipes and packages are
connected, but not the same. Well, it's fair to say that recipe's name
is usually appears as substring in package name, though bitbake really
can build package named arbitrarily from any recipe.
So, what you specify in DEPENDS in recipe name. What you specify in
RDEPENDS and other R* friends in package name.
> export PACKAGE_INSTALL = "... libreadline ..."
> RDEPENDS = "${PACKAGE_INSTALL}"
> That doesn't work either:
BB>>> build display-image
> SHELL: This command needs to parse bbfiles...
> NOTE: Using cache in
> '/bulk/home/rob/oe/dev/build-epia/tmp/cache/rob-epia'
> NOTE: Handling BitBake files: | (4243/4243) [100 %]
> NOTE: Parsing finished. 3315 cached, 1 parsed, 196 skipped, 731 masked.
> SHELL: Building display-image
> ERROR: Nothing provides runtime dependency libreadline
> NOTE: no buildable providers for display-image
> Neither does 'libreadline4'.
There's no magic, let's see together: explode
libreadline4_4.3-r3_i586.ipk you have (it's essentiall .deb; if in
doubt, use ar followed by tar -z). Look for DEBIAN/control file:
----
Provides: libreadline4
----
that's in addition to implicit provision of package name (which
matches with explicit one here).
So, libreadline4 must work.
General hint: if you have any weird problems with packaging images,
first dumb thing you can try is to remove Packages* files and retry.
That's because ipkg and ipkg-utils have bugs tracking actual state
of package. For example, each time you do "bitbake -c rebuild", and
then create image with that package(s), you *must* kill Packages*.
> I looked at how all the other images/tasks do this, but it seems readline is
> not RDEPENDed anywhere...?
> How should I do this, or where to RTFM, if explained there?
> Cheers!
> Rob
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-02-22 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 11:32 How to specify RDEPENDS properly? Rob Kramer
2007-02-22 12:14 ` Paul Sokolovsky [this message]
2007-02-22 12:24 ` Koen Kooi
2007-02-22 12:56 ` Rob Kramer
2007-02-22 12:51 ` Richard Purdie
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=109483350.20070222141407@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
--cc=robk@starhub.net.sg \
/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.