From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Paulo De Sousa Neves (Nokia - PL/Wroclaw)"
<paulo.de_sousa_neves@nokia.com>,
Paulo Neves <ptsneves@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Fix COMPATIBLE_MACHINE for -native recipe variants.
Date: Mon, 15 Jan 2018 11:05:28 +0000 [thread overview]
Message-ID: <1516014328.29722.227.camel@linuxfoundation.org> (raw)
In-Reply-To: <d7600f26-373a-7ca9-cbaa-97dfac3bd86d@nokia.com>
On Mon, 2018-01-15 at 09:01 +0100, Paulo De Sousa Neves (Nokia -
PL/Wroclaw) wrote:
> Hello Richard,
>
> My problem is that I have the PV expansion happens on the recipe, at
> parsing time regardless of it being on the dependency chain or not.
> On
> the other hand, the PV is not expanded if the COMPATIBLE_MACHINE is
> honored. This makes my build significantly faster also, as it avoids
> other expansions altogether.
>
> Coming back to our issue, this means that with the
> COMPATIBLE_MACHINE
> being honored, my recipes work for all cases except when they are in
> native mode.
Native recipes should not be machine dependent so using
COMPATIBLE_MACHINE for this isn't an option.
The good news is its trivial to add your own anonymous python fragment
which does the same thing. Your layer will not pass the layer
compatibility tests should you do that though.
Cheers,
Richard
prev parent reply other threads:[~2018-01-15 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 17:45 [PATCH] Fix COMPATIBLE_MACHINE for -native recipe variants Paulo Neves
2018-01-12 18:04 ` ✗ patchtest: failure for " Patchwork
2018-01-13 17:14 ` [PATCH] " Richard Purdie
[not found] ` <d7600f26-373a-7ca9-cbaa-97dfac3bd86d@nokia.com>
2018-01-15 11:05 ` Richard Purdie [this message]
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=1516014328.29722.227.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paulo.de_sousa_neves@nokia.com \
--cc=ptsneves@gmail.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