summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-06-24 15:35:15 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-08-13 12:18:35 (GMT)
commit222a9cfa34811fdba7f00fa0c59b12adfd103d68 (patch)
treeb93ac77abba5b50b0ce5fc3d8d590aae016e6c30 /documentation/adt-manual
parentb9bf10a5b242b592b922966baa9cf4e1b7ad220f (diff)
downloadpoky-222a9cfa34811fdba7f00fa0c59b12adfd103d68.tar.gz
ref-manual, adt-manual: Added links to SDKMACHINE variable.
Now that a glossary entry for SDKMACHINE exists, I needed to create some links to it where referenced in the ref-manual and the adt-manual. (From yocto-docs rev: 6efe13bcda22276e5ef71ebafff6f91961b34679) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/adt-manual')
-rw-r--r--documentation/adt-manual/adt-prepare.xml12
1 files changed, 7 insertions, 5 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index e2eb2af..a2a439d 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -91,8 +91,8 @@
91 <para> 91 <para>
92 If you use BitBake to generate the ADT Installer tarball, you must 92 If you use BitBake to generate the ADT Installer tarball, you must
93 <filename>source</filename> the environment setup script 93 <filename>source</filename> the environment setup script
94 (<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>) 94 (<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>)
95 located in the Source Directory before running the 95 located in the Source Directory before running the
96 BitBake command that creates the tarball. 96 BitBake command that creates the tarball.
97 </para> 97 </para>
98 98
@@ -289,10 +289,12 @@
289 In particular, you need to be sure the 289 In particular, you need to be sure the
290 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> 290 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
291 variable matches the architecture for which you are 291 variable matches the architecture for which you are
292 building and that the <filename>SDKMACHINE</filename> 292 building and that the
293 <ulink url='&YOCTO_DOCS_REF_URL;#var-SDKMACHINE'><filename>SDKMACHINE</filename></ulink>
293 variable is correctly set if you are building 294 variable is correctly set if you are building
294 a toolchain for an architecture that differs from your 295 a toolchain designed to run on an architecture that
295 current development host machine.</para> 296 differs from your current development host machine
297 (i.e. the build machine).</para>
296 <para>When the BitBake command 298 <para>When the BitBake command
297 completes, the toolchain installer will be in 299 completes, the toolchain installer will be in
298 <filename>tmp/deploy/sdk</filename> in the Build 300 <filename>tmp/deploy/sdk</filename> in the Build