mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 12:29:55 +00:00
Code Issues Projects Releases Wiki Activity

ref-manual, dev-manual: Clarification of "native" and "sdknative"

Browse Source 
Fixes [YOCTO #8620]

I went through and made some judgement calls on the use of
"native" and "sdknative".  I tried to make sure that the reader
understood the real meaning of these terms.

(From yocto-docs rev: d711e8c6dfb32a4ad79e9d11dbf44fbc759d0245)

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-16 15:42:55 -08:00
committed by Richard Purdie
parent 952bcc7fd5
commit c5b4f69821
8 changed files with 98 additions and 71 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/ref-manual/introduction.xml
+5 -2
View File
@@ -450,7 +450,9 @@
$ sh poky-glibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh
</literallayout>
During execution, a prompt appears that allows you to
choose the installation directory.
choose the installation directory for these tools
designed to run on the target machine
(<link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>).
For example, you could choose the following:
<literallayout class='monospaced'>
/home/<replaceable>your-username</replaceable>/buildtools
@@ -530,7 +532,8 @@
<listitem><para>
On the machine that does not meet the requirements,
run the <filename>.sh</filename> file
to install the tools.
to install the tools built to run on the target machine
(<link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>).
Here is an example:
<literallayout class='monospaced'>
$ sh poky-glibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh