From: Chong Lu <Chong.Lu@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] dbus: fix ptest issue
Date: Tue, 5 Aug 2014 18:07:50 +0800 [thread overview]
Message-ID: <53E0ACF6.1040107@windriver.com> (raw)
In-Reply-To: <1407232384.6981.75.camel@ted>
On 08/05/2014 05:53 PM, Richard Purdie wrote:
> On Tue, 2014-08-05 at 16:33 +0800, Chong Lu wrote:
>> We use PTEST_ENABLED to decide whether build ptest package, so inherit
>> ptest.bbclass in dbus.inc in order to using PTEST_ENABLED variable.
>> Remove PACKAGES and ALLOW_EMPTY, since they have been defined in ptest.bbclass.
>>
>> Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
>> ---
>> meta/recipes-core/dbus/dbus.inc | 7 +++++--
>> 1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc
>> index d38ba7e..6268103 100644
>> --- a/meta/recipes-core/dbus/dbus.inc
>> +++ b/meta/recipes-core/dbus/dbus.inc
>> @@ -8,10 +8,13 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=10dded3b58148f3f1fd804b26354af3e \
>> DEPENDS = "expat virtual/libintl"
>> RDEPENDS_dbus_class-native = ""
>> RDEPENDS_dbus_class-nativesdk = ""
>> -PACKAGES += "${@bb.utils.contains('PTEST_ENABLED', '1', 'dbus-ptest', '', d)}"
>> -ALLOW_EMPTY_dbus-ptest = "1"
>
> I don't think you've understood what this is doing, its conditionally
> building the separate dbus-ptest recipe, if ptest is enabled.
>
> Why is it separate? dbus-ptest needs glib and glib needs dbus. Your
> patch doesn't seem to account for any of that.
>
> "fix ptest issue" is far too vague as a summary of this patch too.
>
> Cheers,
>
> Richard
>
>
>
Hi Richard,
Previously, we use DISTRO_FEATURES to decide whether build ptest, but we
use PTEST_ENABLED now.
PTEST_ENABLED defined in ptest.bbclass. we did't inherit ptest in dbus
recipes, this cause we can't build dbus-ptest package.
Based on above reason, I just send this patch to fix this issue. Or do
you have a better way?
Best Regards
Chong
next prev parent reply other threads:[~2014-08-05 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 8:33 [PATCH 0/3] fix several ptest issues Chong Lu
2014-08-05 8:33 ` [PATCH 1/3] perl: fix the output format of all tests Chong Lu
2014-08-11 1:19 ` Chong Lu
2014-08-05 8:33 ` [PATCH 2/3] strace: fix ptest execution failure Chong Lu
2014-08-11 1:19 ` Chong Lu
2014-08-05 8:33 ` [PATCH 3/3] dbus: fix ptest issue Chong Lu
2014-08-05 9:53 ` Richard Purdie
2014-08-05 10:07 ` Chong Lu [this message]
2014-08-05 10:16 ` Paul Eggleton
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=53E0ACF6.1040107@windriver.com \
--to=chong.lu@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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