sdk-manual: Updated workflow step on getting the image

Provided better instructions and accounted for the fact that it
is just this workflow here that is assuming the need for a
YP-built image.

(From yocto-docs rev: a05091768c914817ed262b15d39e7c9b54a5b863)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2018-06-14 10:12:22 -07:00
committed by Richard Purdie
parent 79081fa07c
commit 190702642b

View File

@@ -68,11 +68,12 @@
</para></listitem>
<listitem><para>
<emphasis>Secure the Yocto Project Kernel Target Image</emphasis>:
You must have a target kernel image that has been built
using the OpenEmbedded build system.</para>
<para>Depending on whether the Yocto Project has a
pre-built image that matches your target architecture
This example workflow assumes application development on
top of an image built using the Yocto Project.
Depending on whether you are using a pre-built image
that matches your target architecture or you are using an
image you build using the
<ulink url='&YOCTO_DOCS_REF_URL;#build-system-term'>OpenEmbedded Build System</ulink>
and where you are going to run the image while you
develop your application (QEMU or real hardware), the
area from which you get the image differs.
@@ -105,7 +106,8 @@
Development Manual for an example.
You can also see the
"<ulink url='https://wiki.yoctoproject.org/wiki/TipsAndTricks/RunningEclipseAgainstBuiltImage#Making_a_Suitable_Qemux86_Image'>Making a Suitable Qemux86 Image</ulink>"
wiki for steps needed to build the image for QEMU.
wiki for steps needed to build an image suitable
for QEMU and for debugging within the Eclipse IDE.
</para></listitem>
</itemizedlist>
</para></listitem>