mirror of
https://git.yoctoproject.org/poky
synced 2026-02-26 19:39:40 +01:00
ref-manual: Updated STAGING_DIR_HOST variable description.
Fixed some grammar issues. (From yocto-docs rev: 5d19e2102d1251dd4fa561995c29191c1489f7fc) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
2029d463a7
commit
8a2291f5e7
@@ -13618,11 +13618,12 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
Specifies the path to the sysroot directory for the system
|
||||
that the component is built to run on (the system that hosts
|
||||
the component).
|
||||
For most recipes, this sysroot is the one that the recipe's
|
||||
on which the component is built to run (the system that
|
||||
hosts the component).
|
||||
For most recipes, this sysroot is the one in which that
|
||||
recipe's
|
||||
<link linkend='ref-tasks-populate_sysroot'><filename>do_populate_sysroot</filename></link>
|
||||
task copies files into.
|
||||
task copies files.
|
||||
Exceptions include <filename>-native</filename> recipes,
|
||||
where the <filename>do_populate_sysroot</filename> task
|
||||
instead uses
|
||||
@@ -13631,17 +13632,19 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
<filename>STAGING_DIR_HOST</filename> can have the
|
||||
following values:
|
||||
<itemizedlist>
|
||||
<listitem><para>For recipes building for the target
|
||||
machine, the value is
|
||||
<listitem><para>
|
||||
For recipes building for the target machine, the
|
||||
value is
|
||||
"${<link linkend='var-STAGING_DIR'>STAGING_DIR</link>}/${<link linkend='var-MACHINE'>MACHINE</link>}".
|
||||
</para></listitem>
|
||||
<listitem><para>For native recipes building
|
||||
for the build host, the value is empty given the
|
||||
assumption that when building for the build host,
|
||||
the build host's own directories should be used.
|
||||
<note><para>
|
||||
<filename>-native</filename> recipes are not
|
||||
installed into host paths like such as
|
||||
<listitem><para>
|
||||
For native recipes building for the build host, the
|
||||
value is empty given the assumption that when
|
||||
building for the build host, the build host's own
|
||||
directories should be used.
|
||||
<note>
|
||||
<para><filename>-native</filename> recipes are
|
||||
not installed into host paths like such as
|
||||
<filename>/usr</filename>.
|
||||
Rather, these recipes are installed into
|
||||
<filename>STAGING_DIR_NATIVE</filename>.
|
||||
@@ -13657,7 +13660,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
example, GCC's <filename>-isystem</filename>
|
||||
option.</para>
|
||||
|
||||
<para>This emphasizes that the
|
||||
<para>Thus, the emphasis is that the
|
||||
<filename>STAGING_DIR*</filename> variables
|
||||
should be viewed as input variables by tasks
|
||||
such as
|
||||
@@ -13671,7 +13674,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
<filename>-native</filename> recipes, as
|
||||
they make use of host headers and libraries.
|
||||
</para>
|
||||
</note>
|
||||
</note>
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
Reference in New Issue
Block a user