From: Chong Lu <Chong.Lu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] dbus: fix a hard dependency about dbus-ptest
Date: Thu, 13 Mar 2014 17:54:03 +0800 [thread overview]
Message-ID: <5321803B.90400@windriver.com> (raw)
In-Reply-To: <CAJTo0LZ_OjXVhoNv6wk085=5vY=i64_8T6s=Tef5h7qgFC5Sfw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On 03/06/2014 06:04 PM, Burton, Ross wrote:
> On 6 March 2014 08:06, Chong Lu <Chong.Lu@windriver.com> wrote:
>> +PACKAGES += "dbus-ptest"
>> +ALLOW_EMPTY_${PN}-ptest = "1"
>> +RDEPENDS_${PN}-ptest = "${@base_contains('IMAGE_FEATURES', 'ptest-pkgs', 'dbus-test-ptest', 'dbus-test', d)}"
Hi Ross,
Do you have any suggestion about this issue?
If we don't check IMAGE_FEATURES, I have no way to resolve this problem
that only build but not install ptest. I'm very confused.
Best Regards
Chong
> Nice idea, but wouldn't a more correct solution be to have dbus-ptest
> added to PACKAGES conditionally (instead of always generating
> dbus-ptest and conditionally adding the dependency)?
>
> Ross
> Clearly I wasn't thinking clearly last week. You can't check
> IMAGE_FEATURES in a non-image recipe so this isn't a good solution.
>
> Ross
>
>
[-- Attachment #2: Type: text/html, Size: 1872 bytes --]
next prev parent reply other threads:[~2014-03-13 9:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 8:06 [PATCH 0/1] dbus: fix a hard dependency about dbus-ptest Chong Lu
2014-03-06 8:06 ` [PATCH 1/1] " Chong Lu
2014-03-06 10:04 ` Burton, Ross
2014-03-07 2:13 ` Chong Lu
2014-03-10 11:51 ` Burton, Ross
2014-03-13 9:54 ` Chong Lu [this message]
2014-03-13 10:01 ` Paul Eggleton
2014-03-13 10:48 ` Paul Eggleton
2014-03-14 9:14 ` Chong Lu
2014-03-14 10:12 ` Paul Eggleton
2014-03-17 2:09 ` Chong Lu
2014-03-17 10:44 ` Paul Eggleton
2014-03-17 11:05 ` Paul Eggleton
2014-03-18 7:12 ` Chong Lu
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=5321803B.90400@windriver.com \
--to=chong.lu@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.