From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: basic bitbake commands to create an SDK?
Date: Tue, 25 Oct 2016 15:18:27 +1300 [thread overview]
Message-ID: <17591012.2y05genbPg@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1610240549440.28159@ca624034.mitel.com>
On Mon, 24 Oct 2016 05:51:16 Robert P. J. Day wrote:
> On Sat, 22 Oct 2016, Khem Raj wrote:
> > I would recommend to try using eSDK, which can be generated using
> > -cpopulate_sdk_ext see
> >
> > https://wiki.yoctoproject.org/wiki/Application_Development_with_Extensible
> > _SDK
> just reading up on eSDKs now, am i correct in assuming that if i
> have the time and space to build an eSDK, there is no downside
> compared to building a standard SDK? as in, i don't lose anything from
> the standard SDK, i just get a richer feature set, etc.
Mostly correct, especially for master/morty where we sorted out the lack of
gdb and a few scripts required to support the Eclipse plugin. There are
differences though - please see the introduction of the latest SDK manual [1]
for a comparison chart.
Cheers,
Paul
[1] http://www.yoctoproject.org/docs/latest/sdk-manual/sdk-manual.html#sdk-manual-intro
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2016-10-25 2:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 16:05 basic bitbake commands to create an SDK? Robert P. J. Day
2016-10-22 16:37 ` Khem Raj
2016-10-22 16:53 ` Robert P. J. Day
2016-10-22 16:55 ` Khem Raj
2016-10-22 17:03 ` Robert P. J. Day
2016-10-25 18:29 ` Denys Dmytriyenko
2016-10-22 17:24 ` Robert P. J. Day
2016-10-25 1:01 ` Paul Eggleton
2016-10-24 9:51 ` Robert P. J. Day
2016-10-25 2:18 ` Paul Eggleton [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=17591012.2y05genbPg@peggleto-mobl.ger.corp.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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