summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual
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 /documentation/dev-manual
parent3853dc7fd0001b1ed1abe7729c943abb8f8b314f (diff)
downloadpoky-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>
Diffstat (limited to 'documentation/dev-manual')
-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 12a62f467d..b5274b8452 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -25,7 +25,7 @@
25 <trademark class='trade'>Eclipse</trademark> IDE, 25 <trademark class='trade'>Eclipse</trademark> IDE,
26 see the 26 see the
27 <ulink url='&YOCTO_DOCS_ADT_URL;'> 27 <ulink url='&YOCTO_DOCS_ADT_URL;'>
28 The Yocto Project Application Development Toolkit (ADT) User's Guide</ulink>. 28 The Yocto Project Application Developer's Guide</ulink>.
29 </para></listitem> 29 </para></listitem>
30 <listitem><para><emphasis>Temporary Source Code Modification:</emphasis> 30 <listitem><para><emphasis>Temporary Source Code Modification:</emphasis>
31 Direct modification of temporary source code is a convenient development model 31 Direct modification of temporary source code is a convenient development model
@@ -526,11 +526,12 @@
526 526
527 <para> 527 <para>
528 Application development involves creation of an application that you want to be able 528 Application development involves creation of an application that you want to be able
529 to run on your target hardware, which is running a Yocto Project kernel image. 529 to run on your target hardware, which is running a kernel image created using the
530 The Yocto Project provides an Application Development Toolkit (ADT) that 530 OpenEmbedded build system.
531 facilitates quick development and integration of your application into its run-time environment. 531 The Yocto Project provides an Application Development Toolkit (ADT) and
532 Using the ADT you can employ cross-development toolchains designed for your target hardware 532 stand-alone cross-development toolchains that
533 to compile and link your application. 533 facilitate quick development and integration of your application into its run-time environment.
534 Using the ADT and toolchains, you can compile and link your application.
534 You can then deploy your application to the actual hardware or to the QEMU emulator for testing. 535 You can then deploy your application to the actual hardware or to the QEMU emulator for testing.
535 If you are familiar with the popular Eclipse IDE, you can use an Eclipse Yocto Plug-in to 536 If you are familiar with the popular Eclipse IDE, you can use an Eclipse Yocto Plug-in to
536 allow you to develop, deploy, and test your application all from within Eclipse. 537 allow you to develop, deploy, and test your application all from within Eclipse.
@@ -548,11 +549,8 @@
548 549
549 <para> 550 <para>
550 To help you understand how application development works using the ADT, this section 551 To help you understand how application development works using the ADT, this section
551 provides an overview of the general development process. 552 provides an overview of the general development process and a detailed example of the process
552 If you want to see a detailed example of the process as it is used from within the Eclipse 553 as it is used from within the Eclipse IDE.
553 IDE, see
554 <ulink url='&YOCTO_DOCS_ADT_URL;'>
555 The Application Development Toolkit (ADT) User's Manual</ulink>.
556 </para> 554 </para>
557 555
558 <para> 556 <para>
@@ -610,7 +608,7 @@
610 For information on how to install the ADT, see the 608 For information on how to install the ADT, see the
611 "<ulink url='&YOCTO_DOCS_ADT_URL;#using-the-adt-installer'>Using the ADT Installer</ulink>" 609 "<ulink url='&YOCTO_DOCS_ADT_URL;#using-the-adt-installer'>Using the ADT Installer</ulink>"
612 section 610 section
613 in the Yocto Project Application Development (ADT) User's Manual.</para></listitem> 611 in the Yocto Project Application Developer's Guide.</para></listitem>
614 <listitem><para><emphasis>If Applicable, Secure the Target Root Filesystem</emphasis>: 612 <listitem><para><emphasis>If Applicable, Secure the Target Root Filesystem</emphasis>:
615 If you choose not to install the ADT using the ADT Installer, 613 If you choose not to install the ADT using the ADT Installer,
616 you need to find and download the 614 you need to find and download the
@@ -643,12 +641,12 @@
643 </para> 641 </para>
644 </section> 642 </section>
645 643
646 <section id='workflow-without-adt'> 644 <section id='workflow-using-stand-alone-cross-development-toolchains'>
647 <title>Workflow Without ADT</title> 645 <title>Workflow Using Stand-alone Cross-development Toolchains</title>
648 646
649 <para> 647 <para>
650 If you want to develop an application outside of the Yocto Project ADT environment, you 648 If you want to develop an application without prior installation of the ADT, you
651 can still employ the cross-development toolchain, the QEMU emulator, and a number of supported 649 still can employ the cross-development toolchain, the QEMU emulator, and a number of supported
652 target image files. 650 target image files.
653 You just need to follow these general steps: 651 You just need to follow these general steps:
654 <orderedlist> 652 <orderedlist>
@@ -656,13 +654,13 @@
656 For information on how to install the toolchain, see the 654 For information on how to install the toolchain, see the
657 "<ulink url='&YOCTO_DOCS_ADT_URL;#using-an-existing-toolchain-tarball'>Using a Cross-Toolchain Tarball</ulink>" 655 "<ulink url='&YOCTO_DOCS_ADT_URL;#using-an-existing-toolchain-tarball'>Using a Cross-Toolchain Tarball</ulink>"
658 section 656 section
659 in the Yocto Project Application Development (ADT) User's Manual.</para></listitem> 657 in the Yocto Project Application Developer's Manual.</para></listitem>
660 <listitem><para><emphasis>Download the Target Image:</emphasis> The Yocto Project supports 658 <listitem><para><emphasis>Download the Target Image:</emphasis> The Yocto Project supports
661 several target architectures and has many pre-built kernel images and root filesystem 659 several target architectures and has many pre-built kernel images and root filesystem
662 images.</para> 660 images.</para>
663 <para>If you are going to develop your application on hardware, go to the 661 <para>If you are going to develop your application on hardware, go to the
664 <ulink url='&YOCTO_MACHINES_DL_URL;'> 662 <ulink url='&YOCTO_MACHINES_DL_URL;'><filename>machines</filename></ulink>
665 <filename>machines</filename></ulink> download area and choose a target machine area 663 download area and choose a target machine area
666 from which to download the kernel image and root filesystem. 664 from which to download the kernel image and root filesystem.
667 This download area could have several files in it that support development using 665 This download area could have several files in it that support development using
668 actual hardware. 666 actual hardware.
@@ -671,16 +669,16 @@
671 Be sure to get the files you need for your particular development process.</para> 669 Be sure to get the files you need for your particular development process.</para>
672 <para>If you are going to develop your application and then run and test it using the QEMU 670 <para>If you are going to develop your application and then run and test it using the QEMU
673 emulator, go to the 671 emulator, go to the
674 <ulink url='&YOCTO_QEMU_DL_URL;'> 672 <ulink url='&YOCTO_QEMU_DL_URL;'><filename>machines/qemu</filename></ulink>
675 <filename>machines/qemu</filename></ulink> download area. 673 download area.
676 From this area, go down into the directory for your target architecture 674 From this area, go down into the directory for your target architecture
677 (e.g. <filename>qemux86_64</filename> for an 675 (e.g. <filename>qemux86_64</filename> for an
678 <trademark class='registered'>Intel</trademark>-based 64-bit architecture). 676 <trademark class='registered'>Intel</trademark>-based 64-bit architecture).
679 Download kernel, root filesystem, and any other files you need for your process. 677 Download kernel, root filesystem, and any other files you need for your process.
680 <note>In order to use the root filesystem in QEMU, you need to extract it. 678 <note>In order to use the root filesystem in QEMU, you need to extract it.
681 See the 679 See the
682 "<ulink url='&YOCTO_DOCS_ADT_URL;#extracting-the-root-filesystem'>Extracting the Root Filesystem</ulink>" section for information on how to extract the 680 "<ulink url='&YOCTO_DOCS_ADT_URL;#extracting-the-root-filesystem'>Extracting the Root Filesystem</ulink>"
683 root filesystem.</note></para></listitem> 681 section for information on how to extract the root filesystem.</note></para></listitem>
684 <listitem><para><emphasis>Develop and Test your Application:</emphasis> At this point, 682 <listitem><para><emphasis>Develop and Test your Application:</emphasis> At this point,
685 you have the tools to develop your application. 683 you have the tools to develop your application.
686 If you need to separately install and use the QEMU emulator, you can go to 684 If you need to separately install and use the QEMU emulator, you can go to