From: Mark Hatle <mark.hatle@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Re: Difference of toolchain recipes
Date: Thu, 6 Dec 2012 12:05:11 -0600 [thread overview]
Message-ID: <50C0DE57.2040904@windriver.com> (raw)
In-Reply-To: <CA452391058F6D4E9715FB2C29D9312A0137811C@039-SN2MPN1-021.039d.mgd.msft.net>
On 12/6/12 4:00 AM, Luo Zhenhua-B19537 wrote:
> Can anybody shed some light, please?
>
>
> Best Regards,
>
> Zhenhua
>
>
>> -----Original Message-----
>> From: Luo Zhenhua-B19537
>> Sent: Tuesday, December 04, 2012 11:53 AM
>> To: openembedded-core@lists.openembedded.org; 'yocto@yoctoproject.org'
>> Subject: Difference of toolchain recipes
>>
>> It is a bit confused for the different recipes of toolchian, can somebody
>> help to explain what's the difference for those recipes? E.g. gcc-cross,
>> gcc-cross-canadian, gcc-cross-initial, gcc-cross-intermediate, gcc-
>> crosssdk, gcc-crosssdk-initial, gcc-crosssdk-intermediate, gcc-runtime,
>> etc.
gcc-cross-initial - This is the initial compiler needed to bootstrap the
toolchain to build software on the host for the target. (This is a 'native'
package.)
gcc-cross-intermediate - This is the second stage of the bootstrap process to
build software on the host for the target. (This is a 'native' package.)
gcc-cross - this is the the final stage of the bootstrap process, and results in
the cross compiler to build software on the host for the target. (This is a
'native' package.) If you are replacing the cross compiler toolchain with a
custom version, this is what you must replace.
gcc-runtime - these are the runtime libraries, but from the toolchain
bootstrapping process. This results in a 'target' binary.
gcc-crosssdk-initial/intermediate - stage 1 and 2 of the a cross compiler to
build from the 'host' to the 'sdk'. Often the SDK is not the same target as the
host. (This is a 'native' binary.)
gcc-crosssdk - this the final stage of the SDK compiler. Again, this is to
build on the host, for the sdk. This is a 'native' binary.
gcc-cross-canadian - This is the compiler included with the SDK to build on the
SDK machine creating software for the target. This is an 'nativesdk' package.
>> Is there any document for those description?
Not that I know of.. It's one of those things that you kind of need to know in
order to work with it. It likely should be documented somewhere officially.
--Mark
>>
>>
>> Best Regards,
>>
>> Zhenhua
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2012-12-06 18:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 10:00 Difference of toolchain recipes Luo Zhenhua-B19537
2012-12-06 18:05 ` Mark Hatle [this message]
2012-12-07 3:16 ` Luo Zhenhua-B19537
2012-12-11 21:20 ` Rifenbark, Scott M
2012-12-12 17:08 ` Mark Hatle
2012-12-12 19:33 ` Rifenbark, Scott M
2012-12-12 19:36 ` Bill Traynor
2012-12-12 20:42 ` Rifenbark, Scott M
-- strict thread matches above, loose matches on Subject: below --
2012-12-04 3:52 Luo Zhenhua-B19537
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=50C0DE57.2040904@windriver.com \
--to=mark.hatle@windriver.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.