ref-manual: Updates for nativesdk clarifications.

Fixes [YOCTO #8620]

Added a couple more clarifications for some nativesdk term
uses.  Minor edits to help make things clearer.

(From yocto-docs rev: 38082e1120861332674f97f67966b1f5cec7dc03)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2016-02-24 14:06:54 -08:00 committed by Richard Purdie
parent a882267b58
commit f54fe56fed
2 changed files with 5 additions and 4 deletions

View File

@ -193,8 +193,7 @@
as a prefix, which simplifies a lot of the packaging code for
<filename>nativesdk</filename> recipes.
All custom <filename>nativesdk</filename> recipes, which are
relocatable packages for the native architecture as specified
in
relocatable packages that are native to
<link linkend='var-SDK_ARCH'><filename>SDK_ARCH</filename></link>,
and any references need to be updated to use
<filename>nativesdk-*</filename> instead of

View File

@ -282,8 +282,10 @@
the development tools (e.g., the
<filename>gcc-cross-canadian</filename>),
<filename>binutils-cross-canadian</filename>, and other
<filename>nativesdk-*</filename> tools you need to cross-compile and
test your software.
<filename>nativesdk-*</filename> tools,
which are tools native to the SDK (i.e. native to
<link linkend='var-SDK_ARCH'><filename>SDK_ARCH</filename></link>),
you need to cross-compile and test your software.
The figure shows the commands you use to easily build out this
toolchain.
This cross-development toolchain is built to execute on the