From: Kyle Farnsworth <kyle@farnsworthtech.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: SDK meta-toolchain
Date: Tue, 07 May 2013 14:33:49 -0500 [thread overview]
Message-ID: <5189571D.3030909@farnsworthtech.com> (raw)
In-Reply-To: <51894960.6070406@windriver.com>
On 05/07/2013 01:35 PM, Mark Hatle wrote:
>>> - nativesdk -- runs on the 'sdkhost' (variant called 'crosssdk')
>>
>> Is this related to the SDKMACHINE setting?
>>
>
> Yes that's the variable I was thinking of. You can build an SDK for
> 'i586' on your x86_64 host for instance.
>
So in my case, since I did not specify SDKMACHINE, it is creating a
toolchain that compiles source into x86_64 executables so it can build
the host tools (i.e automake) on the targeted SDK machine. And it has
nothing to do with the targeted device cross-compile toolchain?
next prev parent reply other threads:[~2013-05-07 19:51 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
2013-05-07 18:21 ` Trevor Woerner
2013-05-07 18:35 ` Mark Hatle
2013-05-07 19:33 ` Kyle Farnsworth [this message]
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=5189571D.3030909@farnsworthtech.com \
--to=kyle@farnsworthtech.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