sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual: Updated "Sharing Files Between Recipes" 

Updated text for sysroot terminology, and clarity.
Fixed a capitalization error.

(From yocto-docs rev: 2ee92ccf677135ea47d621d3583a16649e5a9f13)

Signed-off-by: Kristi Rifenbark <kristi.rifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Kristi Rifenbark 2017-08-10 15:07:00 -07:00 committed by Richard Purdie
parent 5826fabe6f
commit a2712c3752
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -3192,7 +3192,7 @@
the build host.
For example, an application linking to a common library needs
access to the library itself and its associated headers.
The way this access is accomplished is by populating sysroot
The way this access is accomplished is by populating a sysroot
with files.
Each recipe has two sysroots in its work directory, one for
target files
@ -3201,7 +3201,7 @@
(<filename>recipe-sysroot-native</filename>).
<note>
You could find the term "staging" used within the Yocto
project regarding files populating sysroot (e.g. the
project regarding files populating sysroots (e.g. the
<ulink url='&YOCTO_DOCS_REF_URL;#var-STAGING_DIR'><filename>STAGING_DIR</filename></ulink>
variable).
</note>
@ -3235,14 +3235,14 @@
the sysroot.
The following example shows how you could add the
<filename>/opt</filename> directory to the list of
directories:
directories within a recipe:
<literallayout class='monospaced'>
SYSROOT_DIRS += "/opt"
</literallayout>
</para>
<para>
for a more complete description of the
For a more complete description of the
<ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-populate_sysroot'><filename>do_populate_sysroot</filename></ulink>
task and its associated functions, see the
<ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-staging'><filename>staging</filename></ulink>