All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Denys Dmytriyenko <denis@denix.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	yocto@yoctoproject.org, Otavio Salvador <otavio@ossystems.com.br>,
	Denys Dmytriyenko <denys@ti.com>
Subject: Re: Difference between target, cross, native and nativesdk.
Date: Wed, 21 Jan 2015 22:17:31 +0000	[thread overview]
Message-ID: <1421878651.19798.6.camel@linuxfoundation.org> (raw)
In-Reply-To: <20150121213150.GN20639@denix.org>

On Wed, 2015-01-21 at 16:31 -0500, Denys Dmytriyenko wrote:
> On Wed, Jan 21, 2015 at 09:23:35PM +0000, Richard Purdie wrote:
> > On Wed, 2015-01-21 at 14:27 -0500, Denys Dmytriyenko wrote:
> > > On Wed, Jan 21, 2015 at 11:23:38AM -0200, Raphael Philipe wrote:
> > > > I was explained about the difference in a different way.
> > > > 
> > > > cross generates binary for the host architecture. But the way this
> > > > binary is generated depends of the target architecture. Native
> > > > generated binaries that do not depend of the target architecture.
> > > 
> > > Pretty much.
> > > 
> > > But another big difference is that -native packages do not generate IPK, RPM 
> > > or DEB, while -nativesdk, -cross, -crosssdk and -cross-canadian do.
> > 
> > -cross and -crosssdk do not generate packages.
> 
> Yeah, I thought so initially, but then I found depmodwrapper-cross and 
> qemuwrapper-cross packages in my deploy/ipk, which got me confused... They 
> seem to be special cases and only have scripts and not binaries. I wonder if 
> the name is misleading...

More like they shouldn't be getting packaged...

Cheers,

Richard



      reply	other threads:[~2015-01-21 22:18 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é
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 [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=1421878651.19798.6.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=denis@denix.org \
    --cc=denys@ti.com \
    --cc=otavio@ossystems.com.br \
    --cc=paul.eggleton@linux.intel.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.