From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Denys Dmytriyenko <denis@denix.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] virglrenderer: correct REQUIRED_DISTRO_FEATURES
Date: Thu, 11 Jun 2020 15:21:02 +0800 [thread overview]
Message-ID: <fe6bf251-571e-a5ed-53f9-e150f7407b13@windriver.com> (raw)
In-Reply-To: <CANNYZj_YwkQeLNW1VHAhOJXkgyXDW6XcfyM-N4zcrRdp3fJZ7w@mail.gmail.com>
Hi Alex,
On 6/10/20 4:25 PM, Alexander Kanavin wrote:
> On Wed, 10 Jun 2020 at 04:10, Yu, Mingli <mingli.yu@windriver.com
> <mailto:mingli.yu@windriver.com>> wrote:
>
> Hi Alex and Denys,
>
> On 6/10/20 5:50 AM, Denys Dmytriyenko wrote:
> > +1
> >
> > The commit message should explain "why" and not "what", as "what"
> can be
> > easily understood from the code itself.
>
> In fact, the DISTRO_FEATURES setting shouldn't affect native build.
>
> Initially this patch is used to fix below error when opengl not defined
> in DISTRO_FEATURES in my build environment.
> $ bitbake virglrenderer-native
> virglrenderer-native was skipped: missing required distro feature
> 'opengl' (not in DISTRO_FEATURES)
>
>
> This is not an error, but expected behavior. virglrenderer-native only
> works when opengl is in DISTRO_FEATURES and should be skipped otherwise.
Does it mean the DISTRO_FEATURES setting also affects the native build?
If so, please ignore this patch.
Thanks,
>
> Alex
next prev parent reply other threads:[~2020-06-11 7:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 7:15 [PATCH] virglrenderer: correct REQUIRED_DISTRO_FEATURES Yu, Mingli
2020-06-09 7:40 ` [OE-core] " Alexander Kanavin
2020-06-09 21:50 ` Denys Dmytriyenko
2020-06-10 2:09 ` Yu, Mingli
2020-06-10 8:25 ` Alexander Kanavin
2020-06-11 7:21 ` Yu, Mingli [this message]
2020-06-11 8:14 ` Alexander Kanavin
2020-06-11 8:31 ` Yu, Mingli
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=fe6bf251-571e-a5ed-53f9-e150f7407b13@windriver.com \
--to=mingli.yu@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=denis@denix.org \
--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