mirror of
https://git.yoctoproject.org/poky
synced 2026-01-29 21:08:42 +01:00
sdk-manual: Updates to configuring targe options sections
Both Neon and Oxygen needed some changes for correct use of the way we refer to menus and fields. (From yocto-docs rev: 1cb20243194e61b925df6b0a3b136233f1da8a57) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
committed by
Richard Purdie
Richard Purdie
parent
74f4f81f62
commit
48372e1bcc
@@ -504,16 +504,17 @@
|
||||
emulator, or you can choose to run your image on actual
|
||||
hardware.
|
||||
<itemizedlist>
|
||||
<listitem><para><emphasis>QEMU:</emphasis>
|
||||
<listitem><para>
|
||||
<emphasis>QEMU:</emphasis>
|
||||
Select this option if you will be using the
|
||||
QEMU emulator.
|
||||
If you are using the emulator, you also need to
|
||||
locate the kernel and specify any custom
|
||||
options.</para>
|
||||
<para>If you selected the
|
||||
<filename>Build system derived toolchain</filename>,
|
||||
the target kernel you built will be located in
|
||||
the
|
||||
|
||||
<para>If you selected the Build system derived
|
||||
toolchain, the target kernel you built will be
|
||||
located in the
|
||||
<ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>
|
||||
in
|
||||
<filename>tmp/deploy/images/<replaceable>machine</replaceable></filename>
|
||||
@@ -525,10 +526,12 @@
|
||||
followed by the image (e.g.
|
||||
<filename>/home/scottrif/poky/build/tmp/deploy/images/qemux86/bzImage-qemux86.bin</filename>).
|
||||
</para>
|
||||
|
||||
<para>If you selected the standalone pre-built
|
||||
toolchain, the pre-built image you downloaded is
|
||||
located in the directory you specified when you
|
||||
downloaded the image.</para>
|
||||
|
||||
<para>Most custom options are for advanced QEMU
|
||||
users to further customize their QEMU instance.
|
||||
These options are specified between paired
|
||||
@@ -545,16 +548,16 @@
|
||||
The following is an example:
|
||||
<literallayout class='monospaced'>
|
||||
serial ‘<-m 256 -full-screen>’
|
||||
</literallayout></para>
|
||||
<para>
|
||||
</literallayout>
|
||||
Regardless of the mode, Sysroot is already
|
||||
defined as part of the Cross-Compiler Options
|
||||
configuration in the
|
||||
<filename>Sysroot Location:</filename> field.
|
||||
configuration in the "Sysroot Location:" field.
|
||||
</para></listitem>
|
||||
<listitem><para><emphasis>External HW:</emphasis>
|
||||
<listitem><para>
|
||||
<emphasis>External HW:</emphasis>
|
||||
Select this option if you will be using actual
|
||||
hardware.</para></listitem>
|
||||
hardware.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
|
||||
@@ -645,15 +645,13 @@
|
||||
architecture.
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
<emphasis>Selecting the Toolchain
|
||||
Type:</emphasis>
|
||||
<emphasis>Selecting the Toolchain Type:</emphasis>
|
||||
Choose between "Standalone pre-built toolchain"
|
||||
and "Build system derived toolchain" for
|
||||
Cross Compiler Options.
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
<emphasis>Standalone Pre-built Toolchain:
|
||||
</emphasis>
|
||||
<emphasis>Standalone Pre-built Toolchain:</emphasis>
|
||||
Select this type when you are using
|
||||
a stand-alone cross-toolchain.
|
||||
For example, suppose you are an
|
||||
@@ -668,8 +666,7 @@
|
||||
for an existing image.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<emphasis>Build System Derived Toolchain:
|
||||
</emphasis>
|
||||
<emphasis>Build System Derived Toolchain:</emphasis>
|
||||
Select this type if you built the
|
||||
toolchain as part of the
|
||||
<ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>.
|
||||
@@ -779,10 +776,10 @@
|
||||
If you are using the emulator, you also
|
||||
need to locate the kernel and specify any
|
||||
custom options.</para>
|
||||
<para>If you selected the
|
||||
<filename>Build system derived toolchain</filename>,
|
||||
the target kernel you built will be located
|
||||
in the
|
||||
|
||||
<para>If you selected the Build system derived
|
||||
toolchain, the target kernel you built will be
|
||||
located in the
|
||||
<ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>
|
||||
in
|
||||
<filename>tmp/deploy/images/<replaceable>machine</replaceable></filename>
|
||||
@@ -794,11 +791,13 @@
|
||||
Directory path followed by the image (e.g.
|
||||
<filename>/home/scottrif/poky/build/tmp/deploy/images/qemux86/bzImage-qemux86.bin</filename>).
|
||||
</para>
|
||||
|
||||
<para>If you selected the standalone
|
||||
pre-built toolchain, the pre-built image
|
||||
you downloaded is located in the directory
|
||||
you specified when you downloaded the
|
||||
image.</para>
|
||||
|
||||
<para>Most custom options are for advanced
|
||||
QEMU users to further customize their QEMU
|
||||
instance.
|
||||
@@ -817,18 +816,17 @@
|
||||
The following is an example:
|
||||
<literallayout class='monospaced'>
|
||||
serial ‘<-m 256 -full-screen>’
|
||||
</literallayout></para>
|
||||
<para>
|
||||
</literallayout>
|
||||
Regardless of the mode, Sysroot is already
|
||||
defined as part of the Cross-Compiler
|
||||
Options configuration in the
|
||||
<filename>Sysroot Location:</filename>
|
||||
field.
|
||||
Options configuration in the "Sysroot
|
||||
Location:" field.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<emphasis>External HW:</emphasis>
|
||||
Select this option if you will be using
|
||||
actual hardware.</para></listitem>
|
||||
actual hardware.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user