All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joel Winarske" <joel.winarske@gmail.com>
To: Ross Burton <ross@burtonini.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] project that builds target and host
Date: Wed, 13 May 2020 12:28:17 -0700	[thread overview]
Message-ID: <CABKMkPJOBH+b=7DmpSvYH6By+3hXQmxrQ702D7basQAae2q78w@mail.gmail.com> (raw)
In-Reply-To: <CAAnfSTtUAJO=agi0fpBWEt4Q0dEatXXijCfRVrbguVRzQrLAyw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 902 bytes --]

Hi Ross,

Yes I've done what you mention before.

In this case I already have a Target and Native recipe.  The Project
generates a Native artifact when building the Target.  Not resolvable
without major surgery.  This artifact is then required in other Target
recipes.


Joel

On Wed, May 13, 2020, 7:13 AM Ross Burton <ross@burtonini.com> wrote:

> On Wed, 13 May 2020 at 06:03, Joel Winarske <joel.winarske@gmail.com>
> wrote:
> > I have a project that generates a native artifact during the target
> build.  Both the native and target artifacts are needed for other target
> recipes.
> >
> > What's the recommended pattern for handling this?
>
> Either use BBCLASSEXTEND or write a -native recipe, build just the
> native parts in a foo-native recipe and depend on that to build foo
> and other recipes.
>
> For example, glib-2.0 DEPENDS on glib-2.0-native.
>
> Ross
>

[-- Attachment #2: Type: text/html, Size: 1435 bytes --]

  reply	other threads:[~2020-05-13 19:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13  5:02 Joel Winarske
2020-05-13 14:13 ` [yocto] " Ross Burton
2020-05-13 19:28   ` Joel Winarske [this message]
2020-05-13 19:51     ` Ross Burton
2020-05-13 20:05       ` Joel Winarske
2020-05-13 20:46         ` Ross Burton
2020-05-14  5:42           ` Joel Winarske

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='CABKMkPJOBH+b=7DmpSvYH6By+3hXQmxrQ702D7basQAae2q78w@mail.gmail.com' \
    --to=joel.winarske@gmail.com \
    --cc=ross@burtonini.com \
    --cc=yocto@lists.yoctoproject.org \
    --subject='Re: [yocto] project that builds target and host' \
    /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

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.