adt-manual: Remaining mods to clarify xtoolchain env use

Fixes [YOCTO #7133]

Edits to add more clarification for use and role of the
cross-toolchain environment variables established when a user
runs the cross-toolchain environment setup script.

(From yocto-docs rev: 2c3fa3a838a3a8970cd112935e903c96552ed06b)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 6 insertions, 2 deletions

diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 995d589..e75e9c9 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -580,7 +580,8 @@
 
         <para>
             To extract the root filesystem, first <filename>source</filename>
-            the cross-development environment setup script.
+            the cross-development environment setup script to establish
+            necessary environment variables.
             If you built the toolchain in the Build Directory, you will find
             the toolchain environment script in the
             <filename>tmp</filename> directory.
@@ -657,7 +658,10 @@
                 hardware can be passed to <filename>gcc</filename> as a set of
                 compiler options.
                 Those options are set up by the environment script and
-                contained in variables like CC and LD.
+                contained in variables such as
+                <ulink url='&YOCTO_DOCS_REF_URL;#var-CC'><filename>CC</filename></ulink>
+                and
+                <ulink url='&YOCTO_DOCS_REF_URL;#var-LD'><filename>LD</filename></ulink>.
                 This reduces the space needed for the tools.
                 Understand, however, that a sysroot is still needed for every
                 target since those binaries are target-specific.