summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-04-10 12:45:18 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-11 12:22:30 +0100
commit32fdd41ec004cf14e5bd4e938970b09ee57bce07 (patch)
tree27caf0afce6a73c2baa7d7094a46edbec4a3216f
parent52c835c42cfdd705536d0d3826d83dc021a6f69b (diff)
downloadpoky-32fdd41ec004cf14e5bd4e938970b09ee57bce07.tar.gz
dev-manual: Edits to "Workflow Using the ADT and Eclipse" section.
(From yocto-docs rev: 2fec6bbe8b89ce41b4fcd40f2ebaa5fa3fe3687e) 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.xml18
1 files changed, 9 insertions, 9 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index f9efb8b533..452f97694b 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -513,12 +513,12 @@
513 513
514 <para> 514 <para>
515 <orderedlist> 515 <orderedlist>
516 <listitem><para><emphasis>Prepare the Host System for the Yocto Project</emphasis>: 516 <listitem><para><emphasis>Prepare the host system for the Yocto Project</emphasis>:
517 See 517 See
518 "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distribution</ulink>" and 518 "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distribution</ulink>" and
519 "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both 519 "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both
520 in the Yocto Project Quick Start for requirements.</para></listitem> 520 in the Yocto Project Quick Start for requirements.</para></listitem>
521 <listitem><para><emphasis>Secure the Yocto Project Kernel Target Image</emphasis>: 521 <listitem><para><emphasis>Secure the Yocto Project kernel target image</emphasis>:
522 You must have a target kernel image that has been built using the OpenEmbedded 522 You must have a target kernel image that has been built using the OpenEmbedded
523 build system.</para> 523 build system.</para>
524 <para>Depending on whether the Yocto Project has a pre-built image that matches your target 524 <para>Depending on whether the Yocto Project has a pre-built image that matches your target
@@ -550,14 +550,14 @@
550 The ADT provides a target-specific cross-development toolchain, the root filesystem, 550 The ADT provides a target-specific cross-development toolchain, the root filesystem,
551 the QEMU emulator, and other tools that can help you develop your application. 551 the QEMU emulator, and other tools that can help you develop your application.
552 While it is possible to get these pieces separately, the ADT Installer provides an 552 While it is possible to get these pieces separately, the ADT Installer provides an
553 easy method. 553 easy, inclusive method.
554 You can get these pieces by running an ADT installer script, which is configurable. 554 You can get these pieces by running an ADT installer script, which is configurable.
555 For information on how to install the ADT, see the 555 For information on how to install the ADT, see the
556 "<ulink url='&YOCTO_DOCS_ADT_URL;#using-the-adt-installer'>Using the ADT Installer</ulink>" 556 "<ulink url='&YOCTO_DOCS_ADT_URL;#using-the-adt-installer'>Using the ADT Installer</ulink>"
557 section 557 section
558 in the Yocto Project Application Developer's Guide.</para></listitem> 558 in the Yocto Project Application Developer's Guide.</para></listitem>
559 <listitem><para><emphasis>If Applicable, Secure the Target Root Filesystem 559 <listitem><para><emphasis>If applicable, secure the target root filesystem
560 and the Cross-development Toolchain</emphasis>: 560 and the Cross-development toolchain</emphasis>:
561 If you choose not to install the ADT using the ADT Installer, 561 If you choose not to install the ADT using the ADT Installer,
562 you need to find and download the appropriate root filesystem and 562 you need to find and download the appropriate root filesystem and
563 the cross-development toolchain.</para> 563 the cross-development toolchain.</para>
@@ -565,7 +565,7 @@
565 for the kernel image. 565 for the kernel image.
566 Depending on the type of image you are running, the root filesystem you need differs. 566 Depending on the type of image you are running, the root filesystem you need differs.
567 For example, if you are developing an application that runs on an image that 567 For example, if you are developing an application that runs on an image that
568 supports Sato, you need to get root filesystem that supports Sato.</para> 568 supports Sato, you need to get a root filesystem that supports Sato.</para>
569 <para>You can find the cross-development toolchains at 569 <para>You can find the cross-development toolchains at
570 <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'><filename>toolchains</filename></ulink>. 570 <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'><filename>toolchains</filename></ulink>.
571 Be sure to get the correct toolchain for your development host and your 571 Be sure to get the correct toolchain for your development host and your
@@ -578,20 +578,20 @@
578 the correct toolchain based on your host development system and your target 578 the correct toolchain based on your host development system and your target
579 architecture. 579 architecture.
580 </para></listitem> 580 </para></listitem>
581 <listitem><para><emphasis>Create and Build your Application</emphasis>: 581 <listitem><para><emphasis>Create and build your application</emphasis>:
582 At this point, you need to have source files for your application. 582 At this point, you need to have source files for your application.
583 Once you have the files, you can use the Eclipse IDE to import them and build the 583 Once you have the files, you can use the Eclipse IDE to import them and build the
584 project. 584 project.
585 If you are not using Eclipse, you need to use the cross-development tools you have 585 If you are not using Eclipse, you need to use the cross-development tools you have
586 installed to create the image.</para></listitem> 586 installed to create the image.</para></listitem>
587 <listitem><para><emphasis>Deploy the Image with the Application</emphasis>: 587 <listitem><para><emphasis>Deploy the image with the application</emphasis>:
588 If you are using the Eclipse IDE, you can deploy your image to the hardware or to 588 If you are using the Eclipse IDE, you can deploy your image to the hardware or to
589 QEMU through the project's preferences. 589 QEMU through the project's preferences.
590 If you are not using the Eclipse IDE, then you need to deploy the application 590 If you are not using the Eclipse IDE, then you need to deploy the application
591 to the hardware using other methods. 591 to the hardware using other methods.
592 Or, if you are using QEMU, you need to use that tool and load your image in for testing. 592 Or, if you are using QEMU, you need to use that tool and load your image in for testing.
593 </para></listitem> 593 </para></listitem>
594 <listitem><para><emphasis>Test and Debug the Application</emphasis>: 594 <listitem><para><emphasis>Test and debug the application</emphasis>:
595 Once your application is deployed, you need to test it. 595 Once your application is deployed, you need to test it.
596 Within the Eclipse IDE, you can use the debugging environment along with the 596 Within the Eclipse IDE, you can use the debugging environment along with the
597 set of user-space tools installed along with the ADT to debug your application. 597 set of user-space tools installed along with the ADT to debug your application.