summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/adt-manual/adt-prepare.xml12
-rw-r--r--documentation/ref-manual/technical-details.xml7
2 files changed, 12 insertions, 7 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index e2eb2afe97..a2a439d01e 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
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index f17291f2cb..17f96b52ff 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -263,7 +263,8 @@
263 The figure shows the commands you use to easily build out this 263 The figure shows the commands you use to easily build out this
264 toolchain. 264 toolchain.
265 This cross-development toolchain is built to execute on the 265 This cross-development toolchain is built to execute on the
266 <filename>SDKMACHINE</filename>, which might or might not be the same 266 <link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>,
267 which might or might not be the same
267 machine as the Build Host. 268 machine as the Build Host.
268 <note> 269 <note>
269 If your target architecture is supported by the Yocto Project, 270 If your target architecture is supported by the Yocto Project,
@@ -320,7 +321,9 @@
320 </para></listitem> 321 </para></listitem>
321 <listitem><para><filename>gcc-cross-canadian</filename>: 322 <listitem><para><filename>gcc-cross-canadian</filename>:
322 The final relocatable cross-compiler. 323 The final relocatable cross-compiler.
323 When run on the <filename>SDKMACHINE</filename>, this tool 324 When run on the
325 <link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>,
326 this tool
324 produces executable code that runs on the target device. 327 produces executable code that runs on the target device.
325 </para></listitem> 328 </para></listitem>
326 </itemizedlist> 329 </itemizedlist>