diff options
Diffstat (limited to 'documentation/adt-manual/adt-intro.xml')
| -rw-r--r-- | documentation/adt-manual/adt-intro.xml | 179 |
1 files changed, 179 insertions, 0 deletions
diff --git a/documentation/adt-manual/adt-intro.xml b/documentation/adt-manual/adt-intro.xml new file mode 100644 index 0000000000..ed13a23a5f --- /dev/null +++ b/documentation/adt-manual/adt-intro.xml | |||
| @@ -0,0 +1,179 @@ | |||
| 1 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" | ||
| 2 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" | ||
| 3 | [<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] > | ||
| 4 | |||
| 5 | <chapter id='adt-intro'> | ||
| 6 | <title>The Application Development Toolkit (ADT)</title> | ||
| 7 | |||
| 8 | <para> | ||
| 9 | Part of the Yocto Project development solution is an Application Development | ||
| 10 | Toolkit (ADT). | ||
| 11 | The ADT provides you with a custom-built, cross-development | ||
| 12 | platform suited for developing a user-targeted product application. | ||
| 13 | </para> | ||
| 14 | |||
| 15 | <para> | ||
| 16 | Fundamentally, the ADT consists of the following: | ||
| 17 | <itemizedlist> | ||
| 18 | <listitem><para>An architecture-specific cross-toolchain and matching | ||
| 19 | sysroot both built by the OpenEmbedded build system. | ||
| 20 | The toolchain and sysroot are based on a | ||
| 21 | <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> | ||
| 22 | configuration and extensions, | ||
| 23 | which allows you to cross-develop on the host machine for the target hardware. | ||
| 24 | </para></listitem> | ||
| 25 | <listitem><para>The Eclipse IDE Yocto Plug-in.</para></listitem> | ||
| 26 | <listitem><para>The Quick EMUlator (QEMU), which lets you simulate target hardware. | ||
| 27 | </para></listitem> | ||
| 28 | <listitem><para>Various user-space tools that greatly enhance your application | ||
| 29 | development experience.</para></listitem> | ||
| 30 | </itemizedlist> | ||
| 31 | </para> | ||
| 32 | |||
| 33 | <section id='the-cross-development-toolchain'> | ||
| 34 | <title>The Cross-Development Toolchain</title> | ||
| 35 | |||
| 36 | <para> | ||
| 37 | The | ||
| 38 | <ulink url='&YOCTO_DOCS_DEV_URL;#cross-development-toolchain'>Cross-Development Toolchain</ulink> | ||
| 39 | consists of a cross-compiler, cross-linker, and cross-debugger | ||
| 40 | that are used to develop user-space applications for targeted | ||
| 41 | hardware. | ||
| 42 | This toolchain is created either by running the ADT Installer | ||
| 43 | script, a toolchain installer script, or through a | ||
| 44 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> | ||
| 45 | that is based on your Metadata configuration or extension for | ||
| 46 | your targeted device. | ||
| 47 | The cross-toolchain works with a matching target sysroot. | ||
| 48 | </para> | ||
| 49 | </section> | ||
| 50 | |||
| 51 | <section id='sysroot'> | ||
| 52 | <title>Sysroot</title> | ||
| 53 | |||
| 54 | <para> | ||
| 55 | The matching target sysroot contains needed headers and libraries for generating | ||
| 56 | binaries that run on the target architecture. | ||
| 57 | The sysroot is based on the target root filesystem image that is built by | ||
| 58 | the OpenEmbedded build system and uses the same Metadata configuration | ||
| 59 | used to build the cross-toolchain. | ||
| 60 | </para> | ||
| 61 | </section> | ||
| 62 | |||
| 63 | <section id='eclipse-overview'> | ||
| 64 | <title>Eclipse Yocto Plug-in</title> | ||
| 65 | |||
| 66 | <para> | ||
| 67 | The Eclipse IDE is a popular development environment and it fully supports | ||
| 68 | development using the Yocto Project. | ||
| 69 | When you install and configure the Eclipse Yocto Project Plug-in into | ||
| 70 | the Eclipse IDE, you maximize your Yocto Project experience. | ||
| 71 | Installing and configuring the Plug-in results in an environment that | ||
| 72 | has extensions specifically designed to let you more easily develop software. | ||
| 73 | These extensions allow for cross-compilation, deployment, and execution of | ||
| 74 | your output into a QEMU emulation session. | ||
| 75 | You can also perform cross-debugging and profiling. | ||
| 76 | The environment also supports a suite of tools that allows you to perform | ||
| 77 | remote profiling, tracing, collection of power data, collection of | ||
| 78 | latency data, and collection of performance data. | ||
| 79 | </para> | ||
| 80 | |||
| 81 | <para> | ||
| 82 | For information about the application development workflow that uses the Eclipse | ||
| 83 | IDE and for a detailed example of how to install and configure the Eclipse | ||
| 84 | Yocto Project Plug-in, see the | ||
| 85 | "<ulink url='&YOCTO_DOCS_DEV_URL;#adt-eclipse'>Working Within Eclipse</ulink>" section | ||
| 86 | of the Yocto Project Development Manual. | ||
| 87 | </para> | ||
| 88 | </section> | ||
| 89 | |||
| 90 | <section id='the-qemu-emulator'> | ||
| 91 | <title>The QEMU Emulator</title> | ||
| 92 | |||
| 93 | <para> | ||
| 94 | The QEMU emulator allows you to simulate your hardware while running your | ||
| 95 | application or image. | ||
| 96 | QEMU is made available a number of ways: | ||
| 97 | <itemizedlist> | ||
| 98 | <listitem><para> | ||
| 99 | If you use the ADT Installer script to install ADT, you can | ||
| 100 | specify whether or not to install QEMU. | ||
| 101 | </para></listitem> | ||
| 102 | <listitem><para> | ||
| 103 | If you have cloned the <filename>poky</filename> Git | ||
| 104 | repository to create a | ||
| 105 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink> | ||
| 106 | and you have sourced the environment setup script, QEMU is | ||
| 107 | installed and automatically available. | ||
| 108 | </para></listitem> | ||
| 109 | <listitem><para> | ||
| 110 | If you have downloaded a Yocto Project release and unpacked | ||
| 111 | it to create a | ||
| 112 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink> | ||
| 113 | and you have sourced the environment setup script, QEMU is | ||
| 114 | installed and automatically available. | ||
| 115 | </para></listitem> | ||
| 116 | <listitem><para> | ||
| 117 | If you have installed the cross-toolchain tarball and you | ||
| 118 | have sourced the toolchain's setup environment script, QEMU | ||
| 119 | is also installed and automatically available. | ||
| 120 | </para></listitem> | ||
| 121 | </itemizedlist> | ||
| 122 | </para> | ||
| 123 | </section> | ||
| 124 | |||
| 125 | <section id='user-space-tools'> | ||
| 126 | <title>User-Space Tools</title> | ||
| 127 | |||
| 128 | <para> | ||
| 129 | User-space tools are included as part of the distribution. | ||
| 130 | You will find these tools helpful during development. | ||
| 131 | The tools include LatencyTOP, PowerTOP, OProfile, Perf, SystemTap, and Lttng-ust. | ||
| 132 | These tools are common development tools for the Linux platform. | ||
| 133 | <itemizedlist> | ||
| 134 | <listitem><para><emphasis>LatencyTOP:</emphasis> LatencyTOP focuses on latency | ||
| 135 | that causes skips in audio, | ||
| 136 | stutters in your desktop experience, or situations that overload your server | ||
| 137 | even when you have plenty of CPU power left. | ||
| 138 | </para></listitem> | ||
| 139 | <listitem><para><emphasis>PowerTOP:</emphasis> Helps you determine what | ||
| 140 | software is using the most power. | ||
| 141 | You can find out more about PowerTOP at | ||
| 142 | <ulink url='https://01.org/powertop/'></ulink>.</para></listitem> | ||
| 143 | <listitem><para><emphasis>OProfile:</emphasis> A system-wide profiler for Linux | ||
| 144 | systems that is capable of profiling all running code at low overhead. | ||
| 145 | You can find out more about OProfile at | ||
| 146 | <ulink url='http://oprofile.sourceforge.net/about/'></ulink>. | ||
| 147 | For examples on how to setup and use this tool, see the | ||
| 148 | "<ulink url='&YOCTO_DOCS_PROF_URL;#profile-manual-oprofile'>OProfile</ulink>" | ||
| 149 | section in the Yocto Project Profiling and Tracing Manual. | ||
| 150 | </para></listitem> | ||
| 151 | <listitem><para><emphasis>Perf:</emphasis> Performance counters for Linux used | ||
| 152 | to keep track of certain types of hardware and software events. | ||
| 153 | For more information on these types of counters see | ||
| 154 | <ulink url='https://perf.wiki.kernel.org/'></ulink>. | ||
| 155 | For examples on how to setup and use this tool, see the | ||
| 156 | "<ulink url='&YOCTO_DOCS_PROF_URL;#profile-manual-perf'>perf</ulink>" | ||
| 157 | section in the Yocto Project Profiling and Tracing Manual. | ||
| 158 | </para></listitem> | ||
| 159 | <listitem><para><emphasis>SystemTap:</emphasis> A free software infrastructure | ||
| 160 | that simplifies information gathering about a running Linux system. | ||
| 161 | This information helps you diagnose performance or functional problems. | ||
| 162 | SystemTap is not available as a user-space tool through the Eclipse IDE Yocto Plug-in. | ||
| 163 | See <ulink url='http://sourceware.org/systemtap'></ulink> for more information | ||
| 164 | on SystemTap. | ||
| 165 | For examples on how to setup and use this tool, see the | ||
| 166 | "<ulink url='&YOCTO_DOCS_PROF_URL;#profile-manual-systemtap'>SystemTap</ulink>" | ||
| 167 | section in the Yocto Project Profiling and Tracing Manual.</para></listitem> | ||
| 168 | <listitem><para><emphasis>Lttng-ust:</emphasis> A User-space Tracer designed to | ||
| 169 | provide detailed information on user-space activity. | ||
| 170 | See <ulink url='http://lttng.org/ust'></ulink> for more information on Lttng-ust. | ||
| 171 | </para></listitem> | ||
| 172 | </itemizedlist> | ||
| 173 | </para> | ||
| 174 | </section> | ||
| 175 | |||
| 176 | </chapter> | ||
| 177 | <!-- | ||
| 178 | vim: expandtab tw=80 ts=4 | ||
| 179 | --> | ||
