From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V3] expect: Add recipe
Date: Mon, 04 Nov 2013 10:01:19 +0000 [thread overview]
Message-ID: <1557371.bvju1MZl3L@helios> (raw)
In-Reply-To: <527542CF.5040909@linux.intel.com>
On Saturday 02 November 2013 11:22:07 Saul Wold wrote:
> > +DEPENDS = "tcl"
> > +RDEPENDS_${PN} = "tcl"
>
> You don't need an RDEPENDS_${PN} if it matches with the DEPENDS
For the sake of others reading, it's not as simple as that. DEPENDS is for
build-time dependencies, RDEPENDS is for runtime dependencies; if tcl is
needed both at build time and at runtime, and the runtime dependency isn't a
shared library dependency, it would be valid to have both in the recipe. It
depends on the situation.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-11-04 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 2:08 [PATCH V3] expect: Add recipe Khem Raj
2013-11-02 18:22 ` Saul Wold
2013-11-04 10:01 ` Paul Eggleton [this message]
2013-11-04 13:31 ` 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=1557371.bvju1MZl3L@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox