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

ref-manual, dev-manual: Clarifying "native" and "sdknative"

Browse Source 
Fixes [YOCTO #8620]

I applied some review comments for the changes made to several
areas in both these manuals.  Minor wording fixes and the
dropping of some changes as directed by Joshua Lock.

(From yocto-docs rev: 71af89da612c37162ba27844c297879d643caf65)

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-23 07:22:52 -08:00
committed by Richard Purdie
parent a1970eb17b
commit 3b410498fe
5 changed files with 27 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/ref-manual/introduction.xml
+2 -5
View File
@@ -450,9 +450,7 @@
$ 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 for these tools
designed to run on the target machine
(<link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>).
choose the installation directory.
For example, you could choose the following:
<literallayout class='monospaced'>
/home/<replaceable>your-username</replaceable>/buildtools
@@ -532,8 +530,7 @@
<listitem><para>
On the machine that does not meet the requirements,
run the <filename>.sh</filename> file
to install the tools built to run on the target machine
(<link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>).
to install the tools.
Here is an example:
<literallayout class='monospaced'>
$ sh poky-glibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh
documentation/ref-manual/migration.xml
+4 -3
View File
@@ -193,9 +193,10 @@
as a prefix, which simplifies a lot of the packaging code for
<filename>nativesdk</filename> recipes.
All custom <filename>nativesdk</filename> recipes, which are
recipes built on the host system to create packages for the
target machine, and any
references need to be updated to use
relocatable packages for the native architecture as specified
in
<link linkend='var-SDK_ARCH'><filename>SDK_ARCH</filename></link>,
and any references need to be updated to use
<filename>nativesdk-*</filename> instead of
<filename>*-nativesdk</filename>.
</para>
documentation/ref-manual/ref-classes.xml
+4 -5
View File
@@ -463,11 +463,10 @@
<para>
The <filename>chrpath</filename> class
is a wrapper around the "chrpath" utility.
This utility is used during the build process for
<filename>nativesdk</filename>, <filename>cross</filename>, and
<filename>cross-canadian</filename> recipes, which run on the host
system to create packages for the target hardware and change
is a wrapper around the "chrpath" utility, which is used during the
build process for <filename>nativesdk</filename>,
<filename>cross</filename>, and
<filename>cross-canadian</filename> recipes to change
<filename>RPATH</filename> records within binaries in order to make
them relocatable.
</para>
documentation/ref-manual/technical-details.xml
+6 -1
View File
@@ -477,7 +477,12 @@
It does not matter if the work directory changes because it should
not affect the output for target packages.
Also, the build process has the objective of making native
(build host) or cross packages (target hardware) relocatable.
or cross packages relocatable.
<note>
Both native and cross packages run on the build host.
However, cross packages generate output for the target
architecture.
</note>
The checksum therefore needs to exclude
<filename>WORKDIR</filename>.
The simplistic approach for excluding the work directory is to set