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>
This commit is contained in:
parent
b9bf10a5b2
commit
222a9cfa34
|
@ -91,8 +91,8 @@
|
||||||
<para>
|
<para>
|
||||||
If you use BitBake to generate the ADT Installer tarball, you must
|
If you use BitBake to generate the ADT Installer tarball, you must
|
||||||
<filename>source</filename> the environment setup script
|
<filename>source</filename> the environment setup script
|
||||||
(<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>)
|
(<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>)
|
||||||
located in the Source Directory before running the
|
located in the Source Directory before running the
|
||||||
BitBake command that creates the tarball.
|
BitBake command that creates the tarball.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
@ -289,10 +289,12 @@
|
||||||
In particular, you need to be sure the
|
In particular, you need to be sure the
|
||||||
<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
|
<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
|
||||||
variable matches the architecture for which you are
|
variable matches the architecture for which you are
|
||||||
building and that the <filename>SDKMACHINE</filename>
|
building and that the
|
||||||
|
<ulink url='&YOCTO_DOCS_REF_URL;#var-SDKMACHINE'><filename>SDKMACHINE</filename></ulink>
|
||||||
variable is correctly set if you are building
|
variable is correctly set if you are building
|
||||||
a toolchain for an architecture that differs from your
|
a toolchain designed to run on an architecture that
|
||||||
current development host machine.</para>
|
differs from your current development host machine
|
||||||
|
(i.e. the build machine).</para>
|
||||||
<para>When the BitBake command
|
<para>When the BitBake command
|
||||||
completes, the toolchain installer will be in
|
completes, the toolchain installer will be in
|
||||||
<filename>tmp/deploy/sdk</filename> in the Build
|
<filename>tmp/deploy/sdk</filename> in the Build
|
||||||
|
|
|
@ -263,7 +263,8 @@
|
||||||
The figure shows the commands you use to easily build out this
|
The figure shows the commands you use to easily build out this
|
||||||
toolchain.
|
toolchain.
|
||||||
This cross-development toolchain is built to execute on the
|
This cross-development toolchain is built to execute on the
|
||||||
<filename>SDKMACHINE</filename>, which might or might not be the same
|
<link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>,
|
||||||
|
which might or might not be the same
|
||||||
machine as the Build Host.
|
machine as the Build Host.
|
||||||
<note>
|
<note>
|
||||||
If your target architecture is supported by the Yocto Project,
|
If your target architecture is supported by the Yocto Project,
|
||||||
|
@ -320,7 +321,9 @@
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para><filename>gcc-cross-canadian</filename>:
|
<listitem><para><filename>gcc-cross-canadian</filename>:
|
||||||
The final relocatable cross-compiler.
|
The final relocatable cross-compiler.
|
||||||
When run on the <filename>SDKMACHINE</filename>, this tool
|
When run on the
|
||||||
|
<link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>,
|
||||||
|
this tool
|
||||||
produces executable code that runs on the target device.
|
produces executable code that runs on the target device.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
Loading…
Reference in New Issue