From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: SDK meta-toolchain
Date: Tue, 7 May 2013 12:41:08 -0500 [thread overview]
Message-ID: <51893CB4.9070304@windriver.com> (raw)
In-Reply-To: <51893B46.3090205@farnsworthtech.com>
On 5/7/13 12:35 PM, Kyle Farnsworth wrote:
> On 05/07/2013 11:36 AM, Mark Hatle wrote:
>> On 5/7/13 11:09 AM, Kyle Farnsworth wrote:
>>> I'm a bit confused about what exactly meta-toolchain is building? It
>>> seems to be bitbaking gcc and creating a toolchain with the prefix
>>> x86_64-oesdk-linux- (default SDK_PREFIX) but I'm not sure what it is.
>>> Is it a cross-compile for my target MACHINE or a compiler for my build
>>> machine? Based on the prefix name I am assuming the latter.
>>
>> 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.
>>
>> * 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.
>>
>> Both of the above have their place, depending on the level of command
>> and control people want.
>>
>> The basic meta-toolchain is just the cross compile toolchain and I
>> believe the libc. meta-toolchain-gmae is an example Gnome Mobile
>> Application Environment.
> Thanks. This a good info. I need to do the targeted SDK. But why is it
> re-creating the cross-compile toolchain with the new prefix and a libc?
> I also have cases where I want to deliver an external toolchain within
> the SDK.
There are three types of packages in oe-core.
- Target -- runs on the target
- native -- runs on the host (variant called 'cross')
- nativesdk -- runs on the 'sdkhost' (variant called 'crosssdk')
The SDK allows you to build SDK software for a host that is different then your
build host. Also the nativesdk is 'glibc' independent, while the native version
is specific to your host. This allows the SDK to be shared with other developers.
--Mark
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2013-05-07 17:59 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
2013-05-07 17:35 ` Kyle Farnsworth
2013-05-07 17:41 ` Mark Hatle [this message]
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=51893CB4.9070304@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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