From 055ee2f78075a8fe00f98fc8e714b94cc2913337 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 31 May 2018 12:11:58 -0700 Subject: [PATCH] sdk-manual: Edits to "Sharing Files Between Recipes" Added a cross-reference to the term "build host". Corrected a subject/verb grammar error. (From yocto-docs rev: 4f5c3a49555601d8a20da1b629a46bde03866e78) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/sdk-manual/sdk-extensible.xml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/documentation/sdk-manual/sdk-extensible.xml b/documentation/sdk-manual/sdk-extensible.xml index 60f52f6bb0..63835f80ea 100644 --- a/documentation/sdk-manual/sdk-extensible.xml +++ b/documentation/sdk-manual/sdk-extensible.xml @@ -1547,12 +1547,14 @@ Recipes often need to use files provided by other recipes on - the build host. + 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 within the extensible SDK is through the sysroot. - One sysroot exists per "machine" for which the SDK is being built. + One sysroot exists per "machine" for which the SDK is being + built. In practical terms, this means a sysroot exists for the target machine, and a sysroot exists for the build host. @@ -1565,7 +1567,7 @@ task within the ${D} directory. - A subset of these files automatically go into the sysroot. + A subset of these files automatically goes into the sysroot. The reason for this limitation is that almost all files that go into the sysroot are cataloged in manifests in order to ensure they can be removed later when a recipe is modified or removed.