All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dominic Sacré" <dominic.sacre@gmx.de>
To: Otavio Salvador <otavio@ossystems.com.br>,
	 Raphael Philipe <rapphil@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	Denys Dmytriyenko <denys@ti.com>, yocto <yocto@yoctoproject.org>
Subject: Re: Difference between target, cross, native and nativesdk.
Date: Thu, 22 Jan 2015 23:31:19 +0100	[thread overview]
Message-ID: <54C17A37.9040104@gmx.de> (raw)
In-Reply-To: <CAP9ODKq85m2Cb_DoVgh9+Wi=zjAJc-MmrGAo58h347zd+UUOgQ@mail.gmail.com>

On 2015-01-21 14:37, Otavio Salvador wrote:
> The fw tools inside of U-Boot qualifies for both target and cross use
> cases. When used in cross or crosssdk, it can be used to change things
> in the generated image (sdcard for example) while in the target case
> it can be used in the runtime system.

I've been wondering about the "u-boot-fw-utils-cross" recipe myself.
When I build the recipe I get what appear to be the correct binaries for
the host architecture, located in the target-specific work directory
(e.g. tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-fw-utils-cross).
However, these binaries don't get installed anywhere other recipes (like
my sdcard image) would be able to find them.

My workaround so far has been to build a native package instead (by
simply adding BBCLASSEXTEND = "native" to the regular "u-boot-fw-utils"
recipe).
This way the binaries get installed to the host's sysroot and are found
just fine, but I feel like I'm missing something about how the cross
recipe should be used properly for this purpose.

Can anyone shed some light on this?


Cheers,

Dominic


  reply	other threads:[~2015-01-22 22:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 11:17 Difference between target, cross, native and nativesdk Raphael Philipe
2015-01-20 12:23 ` Paul Eggleton
2015-01-20 14:39   ` Raphael Philipe
2015-01-20 14:44     ` Paul Eggleton
2015-01-21 13:23       ` Raphael Philipe
2015-01-21 13:37         ` Otavio Salvador
2015-01-22 22:31           ` Dominic Sacré [this message]
2015-01-23 12:54             ` Otavio Salvador
2015-01-26 17:02               ` Dominic Sacré
2015-01-26 17:08               ` Denys Dmytriyenko
2015-01-21 19:27         ` Denys Dmytriyenko
2015-01-21 21:23           ` Richard Purdie
2015-01-21 21:31             ` Denys Dmytriyenko
2015-01-21 22:17               ` Richard Purdie

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=54C17A37.9040104@gmx.de \
    --to=dominic.sacre@gmx.de \
    --cc=denys@ti.com \
    --cc=otavio@ossystems.com.br \
    --cc=paul.eggleton@linux.intel.com \
    --cc=rapphil@gmail.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.