From: Kang Kai <Kai.Kang@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] strace: add configure options libaio and acl
Date: Mon, 1 Jul 2013 09:52:42 +0800 [thread overview]
Message-ID: <51D0E0EA.5040902@windriver.com> (raw)
In-Reply-To: <5322253.NAOJVtts1F@helios>
On 2013年06月29日 01:16, Paul Eggleton wrote:
> On Friday 21 June 2013 16:12:21 Kai Kang wrote:
>> Add strace configure options libaio and acl to enable or disable build
>> with them. Then PACKAGECONFIG can be used to handle dependency.
>>
>> Set "libaio" as a default feature of PACKAGECONFIG.
>> ...
>>
>> +PACKAGECONFIG_class-target ?= "libaio"
>> +PACKAGECONFIG_class-target += "${@base_contains('DISTRO_FEATURES', 'acl',
>> 'acl', '', d)}"
Hi Paul,
> I realise this has already been merged, but I think there are a couple of issues
> with the above. Firstly, for consistency, I think the first option should be
> called "aio" and not "libaio".
OK, I'll update it.
> Secondly, although this seems to work the use
> of overrides, += and ?= together is a little bit confusing. Perhaps the following
> would be a bit clearer:
>
> PACKAGECONFIG_class-target ?= "aio \
> ${@base_contains('DISTRO_FEATURES', 'acl', 'acl', '', d)}"
I considered this way.
When 'acl' in distro feature, I want strace enable acl support. But
PACKAGECONFIG could be overwritten that even 'acl' in distro feature but
not in 'PACKAGECONFIG'.
Thanks,
Kai
>
> Cheers,
> Paul
>
--
Regards,
Neil | Kai Kang
next prev parent reply other threads:[~2013-07-01 1:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 8:12 [PATCH 0/2] V3: Update strace to 4.8 Kai Kang
2013-06-21 8:12 ` [PATCH 1/2] strace: update " Kai Kang
2013-06-21 12:25 ` Richard Purdie
2013-06-21 8:12 ` [PATCH 2/2] strace: add configure options libaio and acl Kai Kang
2013-06-28 17:16 ` Paul Eggleton
2013-07-01 1:52 ` Kang Kai [this message]
2013-07-01 9:45 ` 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=51D0E0EA.5040902@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox