From: Mark Hatle <mark.hatle@windriver.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: SDK meta-toolchain
Date: Tue, 7 May 2013 12:00:58 -0500 [thread overview]
Message-ID: <5189334A.5020206@windriver.com> (raw)
In-Reply-To: <CAHUNapRAZVrC4eKTRiPNaun2wg2bEQs2Qt-x8dA67h9Uvb2NWg@mail.gmail.com>
On 5/7/13 11:49 AM, Trevor Woerner wrote:
> On Tue, May 7, 2013 at 12:36 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
>> There are two ways to generate an SDK.
>>
>> * targeted SDK -- This is a meta-toolchain* recipe that lists -exactly- what
>> is going to be in the SDK. This is great if you want to limit your SDK to
>> specific libraries for your application developers.
>
> Is this the one created using:
>
> $ bitbake meta-toolchain
>
> ?
>
>> * implied / image based SDK -- This type of SDK bases off of what is in the
>> image to generate an SDK that contains all of the libraries that are
>> runnable inside of the image. This is a very simple way to generate an SDK
>> for application developers that -will- match the run-time image.
>
> Is this the one created by:
>
> $ bitbake -c populate_sdk <image>
>
> ?
>
Yes to both questions.
--Mark
next prev parent reply other threads:[~2013-05-07 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 16:09 SDK meta-toolchain Kyle Farnsworth
2013-05-07 16:36 ` Mark Hatle
2013-05-07 16:49 ` Trevor Woerner
2013-05-07 17:00 ` Mark Hatle [this message]
2013-05-07 17:35 ` Kyle Farnsworth
2013-05-07 17:41 ` Mark Hatle
2013-05-07 18:21 ` Trevor Woerner
2013-05-07 18:35 ` Mark Hatle
2013-05-07 19:33 ` Kyle Farnsworth
2013-05-07 20:08 ` Mark Hatle
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=5189334A.5020206@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=twoerner@gmail.com \
/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.