All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ola x Nilsson <ola.x.nilsson@axis.com>
To: Josias Inacio da Silva Filho <josiasinacio@hotmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: devtool modify both target and native recipe
Date: Tue, 24 Sep 2019 12:09:45 +0200	[thread overview]
Message-ID: <jwqy2yef1jq.fsf@axis.com> (raw)
In-Reply-To: <SC1PR80MB4558AF3F33D9C5835EA7B2B2C18F0@SC1PR80MB4558.lamprd80.prod.outlook.com>


On Tue, Sep 17 2019, Josias Inacio da Silva Filho wrote:

> I have a recipe that supports building both native and target, however I noticed only one can be modified at a time.
>
> If I try doing:
> $ devtool modify myrecipe path_x
> $ devtool modify myrecipe-native path_x
>
> It complains saying I can only modify one variant at a time.
>
> The way to get around this issue was to go into build/workspace/appends/myrecipe and change this line:
>
> EXTERNALSRC_pn-myrecipe = path_x
>
> To this:
> EXTERNALSRC = path_x
>
> But I wanted to have a proper solution for this. I also saw this comment in the file:
> # NOTE: We use pn- overrides here to avoid affecting multiple variants in the case where the recipe uses BBCLASSEXTEND

Add a line for the native variant so you get:

EXTERNALSRC_pn-myrecipe = path_x
EXTERNALSRC_pn-myrecipe-native = path_x

Note that this will only work if S != B in your recipe, otherwise you
will probably end up with a mishmash of object files of different
architectures.

If you do use different checkouts

EXTERNALSRC_pn-myrecipe = path_x
EXTERNALSRC_pn-myrecipe-native = path_y

will work for S==B, but then you will have to extract the sources some
other way. devtool extract may work here, but I have not tested myself.

-- 
Ola x Nilsson


      reply	other threads:[~2019-09-24 10:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17  8:15 devtool modify both target and native recipe Josias Inacio da Silva Filho
2019-09-24 10:09 ` Ola x Nilsson [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=jwqy2yef1jq.fsf@axis.com \
    --to=ola.x.nilsson@axis.com \
    --cc=josiasinacio@hotmail.com \
    --cc=yocto@yoctoproject.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 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.