From 79081fa07c63ca58dda840f46c295d04cce42aae Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 14 Jun 2018 09:52:03 -0700 Subject: sdk-manual: Updates to Eclipse Workflow section Updated the "Workflow Using Eclipse" section head to not match so closely the "Working With Eclipse" section heading. TOC appeared funny. Also, updated the step 1 to be more accurate regarding the real need of having a YP build host and where to go to get information on setting it up. (From yocto-docs rev: 1cbca098a2f793bd86b6f73d3d35ce79bdf639f0) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/sdk-manual/sdk-eclipse-project.xml | 57 ++++++++++++++++++------ 1 file changed, 43 insertions(+), 14 deletions(-) (limited to 'documentation/sdk-manual') diff --git a/documentation/sdk-manual/sdk-eclipse-project.xml b/documentation/sdk-manual/sdk-eclipse-project.xml index 3eb85e8ab1..b1ebf54dd0 100644 --- a/documentation/sdk-manual/sdk-eclipse-project.xml +++ b/documentation/sdk-manual/sdk-eclipse-project.xml @@ -12,15 +12,34 @@ application all from within Eclipse. This chapter describes general workflow using the SDK and Eclipse and how to configure and set up Eclipse. + Notes + + + This chapter assumes development of applications on top of + an image prepared using the Yocto Project. + As such, inclusion of a pre-built image or the building of + an image is included in the workflow. + + + The chapter also assumes development on a build host that + is set up to use the Yocto Project. + Realize that you can easily use Eclipse and the Yocto + Project plug-in to develop an application for any number + of images developed and tested on different machines. + + + -
- Workflow Using <trademark class='trade'>Eclipse</trademark> +
+ Application Development Workflow Using <trademark class='trade'>Eclipse</trademark> - The following figure and supporting list summarize the + The following figure and supporting list summarize a general workflow for application development that uses the SDK within the Eclipse IDE. + The application developed runs on top of an image created using + the Yocto Project. @@ -32,20 +51,26 @@ Prepare the Host System for the Yocto Project: + Because this example workflow assumes development on a + system set up to use the Yocto Project, you need to be + sure your + build host + can use the Yocto Project. See the - "Supported Linux Distributions" - and - "Required Packages for the Host Development System" - sections both in the Yocto Project Reference Manual for - requirements. - In particular, be sure your host system has the - xterm package installed. + "Preparing a Build Host" + section in the Yocto Project Development Tasks Manual for + information on how to set up your build host. + + Be sure you install the "xterm" package, which is a + graphical and Eclipse plug-in extra + needed by Eclipse. + - Secure the Yocto Project Kernel Target - Image: + Secure the Yocto Project Kernel Target Image: You must have a target kernel image that has been built using the OpenEmbedded build system. + Depending on whether the Yocto Project has a pre-built image that matches your target architecture and where you are going to run the image while you @@ -78,6 +103,9 @@ "Using devtool to Patch the Kernel" section in the Yocto Project Linux Kernel Development Manual for an example. + You can also see the + "Making a Suitable Qemux86 Image" + wiki for steps needed to build the image for QEMU. @@ -91,10 +119,10 @@ section. - Secure the Target Root Filesystem - and the Cross-Development Toolchain: + Secure the Target Root Filesystem and the Cross-Development Toolchain: You need to find and download the appropriate root filesystem and the cross-development toolchain. + You can find the tarballs for the root filesystem in the same area used for the kernel image. Depending on the type of image you are running, the @@ -102,6 +130,7 @@ For example, if you are developing an application that runs on an image that supports Sato, you need to get a root filesystem that supports Sato. + You can find the cross-development toolchains at toolchains. Be sure to get the correct toolchain for your -- cgit v1.2.3-54-g00ecf