diff options
| author |   Scott Rifenbark <srifenbark@gmail.com> | 2016-02-16 15:42:55 -0800 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-03-03 17:40:11 +0000 |
| commit | c5b4f69821c7b5ef9047c41198535eb900ea7b94 (patch) | |
| tree | 9bf773203722b215065ade66f4d2fbde201d4ffd /documentation/ref-manual/introduction.xml | |
| parent | 952bcc7fd5470e534f71150a5a5b36d8b520679e (diff) | |
| download | openembedded-core-contrib-c5b4f69821c7b5ef9047c41198535eb900ea7b94.tar.gz | |
ref-manual, dev-manual: Clarification of "native" and "sdknative"
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>
Diffstat (limited to 'documentation/ref-manual/introduction.xml')
| -rw-r--r-- | documentation/ref-manual/introduction.xml | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/documentation/ref-manual/introduction.xml b/documentation/ref-manual/introduction.xml index 57e4a25853..750d9c681c 100644 --- a/documentation/ref-manual/introduction.xml +++ b/documentation/ref-manual/introduction.xml @@ -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 |