Yocto Project Discussions
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: Jeff Kaisner <jkaisner@aeronix.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Install native recipe into filesystem
Date: Tue, 19 Nov 2019 20:34:05 -0500	[thread overview]
Message-ID: <56b2962f-22e6-0c20-2cf8-5c76174bb6fb@windriver.com> (raw)
In-Reply-To: <e8888d43e2c44373b8c3affaea368dba@aeronix.com>

On 11/19/19 4:15 PM, Jeff Kaisner wrote:
> We have several executables that can run on the target (ARM64) but also 
> on the host system (x86).  I added the BBCLASSEXTEND = "native" and can 
> build all the recipes in native mode.  

What do you mean here by 'in native mode'? I'd expect that you mean:
    $ bitbake somepackage-native
Right?

A few explanations related to your question are here:
 
https://wiki.yoctoproject.org/wiki/Technical_FAQ#What_does_.22native.22_mean.3F
and here:
 
https://wiki.yoctoproject.org/wiki/Technical_FAQ#Why_are_all_of_these_-native_items_being_built_when_my_host_distro_has_some_of_these_available.3F


 > Once done, I would like to be
 > able to install them on the host system, but don’t see a package for
 > them (or understand that part of the process).

You don't add -native package to the target system; they are for the
build (host) system to help build object files for the target machine.

You can either edit the conf/local.conf file then build a standard image
or define your own image. For the former:
 
https://wiki.yoctoproject.org/wiki/Cookbook:Example:Adding_packages_to_your_OS_image


Additional details are in the YP Mega Manual:
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html

Good luck and welcome to the Yocto Project,

../Randy

> 
> Any help would be appreciated.
> 
> Regards,
> 
> Jeff
> 
> 


-- 
# Randy MacLeod
# Wind River Linux


  reply	other threads:[~2019-11-20  1:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 21:15 Install native recipe into filesystem Jeff Kaisner
2019-11-20  1:34 ` Randy MacLeod [this message]
2019-11-20 11:53 ` Ross Burton

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=56b2962f-22e6-0c20-2cf8-5c76174bb6fb@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=jkaisner@aeronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox