Re: IMHO, cross-compile/toolchain examples should use non-x86 arches
Or in Yocto Project context, we kind of use ADT more inclusive that referring what Mark talked about SDK, the eclipse plug-in and other developers tools. And we don't call out SDK that much.toggle quoted messageShow quoted text
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Mark Hatle
Sent: Monday, December 17, 2012 7:48 AM
Subject: Re: [yocto] IMHO, cross-compile/toolchain examples should use non-x86 arches
On 12/16/12 4:57 PM, Sean Liming wrote:
The biggest clarify problem I've seen is the terms being intermingled. There are clear definitions for each.
Toolchain, the compiler and related tools that enable compiling software for a given target.
SDK - Software Development Kit - On OE-Core this purpose of this is to enable developing software to be run on a specific target environment, generally also constructed from OE-Core. The SDK consists of three primary components:
1) environment setup files - these configure the compilation environment with the right settings
2) nativesdk software - these are applications that run on the -host- system to assist in compiling software for the target (this includes the target toolchain.)
3) target sysroot - The sysroot is the collection of libraries, headers and assorted items that are compiled for the target. A sysroot is setup in a similar fashion as a target's root filesystem.
ADT - Application Developer Tool - This is an Eclipse component that can use the SDK, generated by OE-Core, to enable application development within the Eclipse framework. (I may be slightly wrong on this item, as people have told me in the past there are command line parts to the ADT.... but the ADT itself is -not- the
yocto mailing list