summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-07-23 10:05:44 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-07-24 10:35:33 +0100
commitb742716bc2bf8d9f1d3425c0c6033e67bf8763e7 (patch)
tree454bbd2f0d8db22bc8c2c3d5dd8f38cfdf5e15b7
parent3853dc7fd0001b1ed1abe7729c943abb8f8b314f (diff)
downloadast2050-yocto-poky-b742716bc2bf8d9f1d3425c0c6033e67bf8763e7.zip
ast2050-yocto-poky-b742716bc2bf8d9f1d3425c0c6033e67bf8763e7.tar.gz
documentation/dev-manual/dev-manual-model.xml: Edits for Eclipse insertion
In preparation for taking the Eclipse installation and configuration steps, I have made an edit pass through the section "Workflow Using the ADT and Eclipse". Minor edits performed to integrate the new information. (From yocto-docs rev: 7b4e0ae371b23f329451ac768b7d9eab5931df2d) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-model.xml44
1 files changed, 21 insertions, 23 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 12a62f4..b5274b8 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -25,7 +25,7 @@
<trademark class='trade'>Eclipse</trademark> IDE,
see the
<ulink url='&YOCTO_DOCS_ADT_URL;'>
- The Yocto Project Application Development Toolkit (ADT) User's Guide</ulink>.
+ The Yocto Project Application Developer's Guide</ulink>.
</para></listitem>
<listitem><para><emphasis>Temporary Source Code Modification:</emphasis>
Direct modification of temporary source code is a convenient development model
@@ -526,11 +526,12 @@
<para>
Application development involves creation of an application that you want to be able
- to run on your target hardware, which is running a Yocto Project kernel image.
- The Yocto Project provides an Application Development Toolkit (ADT) that
- facilitates quick development and integration of your application into its run-time environment.
- Using the ADT you can employ cross-development toolchains designed for your target hardware
- to compile and link your application.
+ to run on your target hardware, which is running a kernel image created using the
+ OpenEmbedded build system.
+ The Yocto Project provides an Application Development Toolkit (ADT) and
+ stand-alone cross-development toolchains that
+ facilitate quick development and integration of your application into its run-time environment.
+ Using the ADT and toolchains, you can compile and link your application.
You can then deploy your application to the actual hardware or to the QEMU emulator for testing.
If you are familiar with the popular Eclipse IDE, you can use an Eclipse Yocto Plug-in to
allow you to develop, deploy, and test your application all from within Eclipse.
@@ -548,11 +549,8 @@
<para>
To help you understand how application development works using the ADT, this section
- provides an overview of the general development process.
- If you want to see a detailed example of the process as it is used from within the Eclipse
- IDE, see
- <ulink url='&YOCTO_DOCS_ADT_URL;'>
- The Application Development Toolkit (ADT) User's Manual</ulink>.
+ provides an overview of the general development process and a detailed example of the process
+ as it is used from within the Eclipse IDE.
</para>
<para>
@@ -610,7 +608,7 @@
For information on how to install the ADT, see the
"<ulink url='&YOCTO_DOCS_ADT_URL;#using-the-adt-installer'>Using the ADT Installer</ulink>"
section
- in the Yocto Project Application Development (ADT) User's Manual.</para></listitem>
+ in the Yocto Project Application Developer's Guide.</para></listitem>
<listitem><para><emphasis>If Applicable, Secure the Target Root Filesystem</emphasis>:
If you choose not to install the ADT using the ADT Installer,
you need to find and download the
@@ -643,12 +641,12 @@
</para>
</section>
- <section id='workflow-without-adt'>
- <title>Workflow Without ADT</title>
+ <section id='workflow-using-stand-alone-cross-development-toolchains'>
+ <title>Workflow Using Stand-alone Cross-development Toolchains</title>
<para>
- If you want to develop an application outside of the Yocto Project ADT environment, you
- can still employ the cross-development toolchain, the QEMU emulator, and a number of supported
+ If you want to develop an application without prior installation of the ADT, you
+ still can employ the cross-development toolchain, the QEMU emulator, and a number of supported
target image files.
You just need to follow these general steps:
<orderedlist>
@@ -656,13 +654,13 @@
For information on how to install the toolchain, see the
"<ulink url='&YOCTO_DOCS_ADT_URL;#using-an-existing-toolchain-tarball'>Using a Cross-Toolchain Tarball</ulink>"
section
- in the Yocto Project Application Development (ADT) User's Manual.</para></listitem>
+ in the Yocto Project Application Developer's Manual.</para></listitem>
<listitem><para><emphasis>Download the Target Image:</emphasis> The Yocto Project supports
several target architectures and has many pre-built kernel images and root filesystem
images.</para>
<para>If you are going to develop your application on hardware, go to the
- <ulink url='&YOCTO_MACHINES_DL_URL;'>
- <filename>machines</filename></ulink> download area and choose a target machine area
+ <ulink url='&YOCTO_MACHINES_DL_URL;'><filename>machines</filename></ulink>
+ download area and choose a target machine area
from which to download the kernel image and root filesystem.
This download area could have several files in it that support development using
actual hardware.
@@ -671,16 +669,16 @@
Be sure to get the files you need for your particular development process.</para>
<para>If you are going to develop your application and then run and test it using the QEMU
emulator, go to the
- <ulink url='&YOCTO_QEMU_DL_URL;'>
- <filename>machines/qemu</filename></ulink> download area.
+ <ulink url='&YOCTO_QEMU_DL_URL;'><filename>machines/qemu</filename></ulink>
+ download area.
From this area, go down into the directory for your target architecture
(e.g. <filename>qemux86_64</filename> for an
<trademark class='registered'>Intel</trademark>-based 64-bit architecture).
Download kernel, root filesystem, and any other files you need for your process.
<note>In order to use the root filesystem in QEMU, you need to extract it.
See the
- "<ulink url='&YOCTO_DOCS_ADT_URL;#extracting-the-root-filesystem'>Extracting the Root Filesystem</ulink>" section for information on how to extract the
- root filesystem.</note></para></listitem>
+ "<ulink url='&YOCTO_DOCS_ADT_URL;#extracting-the-root-filesystem'>Extracting the Root Filesystem</ulink>"
+ section for information on how to extract the root filesystem.</note></para></listitem>
<listitem><para><emphasis>Develop and Test your Application:</emphasis> At this point,
you have the tools to develop your application.
If you need to separately install and use the QEMU emulator, you can go to
OpenPOWER on IntegriCloud