diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index 753279cb5b..3e903327a2 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -12708,13 +12708,46 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
following values:
For recipes building for the target
- machine, the value is
- "${STAGING_DIR}/${MACHINE}".
-
+ machine, the value is
+ "${STAGING_DIR}/${MACHINE}".
+
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.
+ 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.
+
+ -native recipes are not
+ installed into host paths like such as
+ /usr.
+ Rather, these recipes are installed into
+ STAGING_DIR_NATIVE.
+ When compiling -native
+ recipes, standard build environment variables
+ such as
+ CPPFLAGS
+ and
+ CFLAGS
+ are set up so that both host paths and
+ STAGING_DIR_NATIVE are
+ searched for libraries and headers using, for
+ example, GCC's -isystem
+ option.
+
+ This emphasizes that the
+ STAGING_DIR* variables
+ should be viewed as input variables by tasks
+ such as
+ do_configure,
+ do_compile,
+ and
+ do_install.
+ Having the real system root correspond to
+ STAGING_DIR_HOST makes
+ conceptual sense for
+ -native recipes, as
+ they make use of host headers and libraries.
+
+ For native SDK
recipes that build for the SDK
@@ -12722,33 +12755,6 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
"${STAGING_DIR}/${MULTIMACH_HOST_SYS}".
-
- -native recipes are not installed
- into host paths like such as /usr.
- Rather, these recipes are installed into
- STAGING_DIR_NATIVE.
- When compiling -native recipes,
- standard build environment variables such as
- CPPFLAGS
- and
- CFLAGS
- are set up so that both host paths and
- STAGING_DIR_NATIVE are searched
- for libraries and headers using, for example,
- GCC's -isystem option.
-
- This emphasizes that the
- STAGING_DIR* variables should be
- viewed as input variables by tasks such as
- do_configure,
- do_compile,
- and
- do_install.
- Having the real system root correspond to
- STAGING_DIR_HOST makes conceptual
- sense for -native recipes, as
- they make use of host headers and libraries.
-