Re: IMHO, cross-compile/toolchain examples should use non-x86 arches

Mark Hatle <mark.hatle@...>

On 12/16/12 4:57 PM, Sean Liming wrote:

My 2c (USD) is for clarity on ADT vs. SDK vs. Toolchain.
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 SDK.)



Sean Liming
Tel: 714-970-7523 / Cell: 858-774-3176

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-
bounces@...] On Behalf Of Robert P. J. Day
Sent: Sunday, December 16, 2012 8:55 AM
To: Yocto discussion list
Subject: [yocto] IMHO, cross-compile/toolchain examples should use non-
x86 arches

a general preference on my part, but i think it would be useful if any
docs that are discussing toolchains or cross-compilation or the like use
*non*-x86 architectures to get the point across.

for example, consider the current application developer's guide.
part of it uses, as an example, the toolchain installer
poky-eglibc-x86_64-i586- while this works just fine, of course, what it
does is
potentially co-mingle both the dev host content and target host content,
making it harder than necessary for the reader to draw a clear distinction
between the two.

if any example related to compilation or a toolchain involves, say, an
target, then it's *immediately* obvious (using the "file"
command) whether something belongs on the dev host or on the target.

also, if you're using x86 for both dev content and target content, you
the risk of an example working by accident since you're picking up
installed tools when you shouldn't be. if you use a non-x86 arch, there's
chance of that happening.

just my $0.02 (Cdn).



Robert P. J. Day Ottawa, Ontario, CANADA

yocto mailing list
yocto mailing list

Join { to automatically receive all group messages.