summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/dev-manual/dev-manual-model.xml41
1 files changed, 22 insertions, 19 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 59c392f9db..63a447d59b 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -161,10 +161,10 @@
161 <filename>mpc8315e</filename>, and <filename>routerstationpro</filename>. 161 <filename>mpc8315e</filename>, and <filename>routerstationpro</filename>.
162 The recipes and configurations for these five BSPs are located and dispersed 162 The recipes and configurations for these five BSPs are located and dispersed
163 within the <link linkend='source-directory'>Source Directory</link>. 163 within the <link linkend='source-directory'>Source Directory</link>.
164 On the other hand, BSP layers for Chief River, Crown Bay, 164 On the other hand, BSP layers for Crown Bay,
165 Crystal Forest, Emenlow, Fish River Island 2, Haswell, 165 Crystal Forest, Emenlow, Fish River Island 2, Haswell,
166 Jasper Forest, N450, NUC DC3217IYE, 166 Jasper Forest, NUC DC3217IYE,
167 Romley, sys940x, Sugar Bay, and tlk exist in their own separate layers 167 Romley, Sugar Bay, and tlk exist in their own separate layers
168 within the larger <filename>meta-intel</filename> layer.</note> 168 within the larger <filename>meta-intel</filename> layer.</note>
169 <para>When you set up a layer for a new BSP, you should follow a standard layout. 169 <para>When you set up a layer for a new BSP, you should follow a standard layout.
170 This layout is described in the 170 This layout is described in the
@@ -672,7 +672,7 @@
672 <title>Installing the Eclipse IDE</title> 672 <title>Installing the Eclipse IDE</title>
673 673
674 <para> 674 <para>
675 It is recommended that you have the Kepler 4.3 version of 675 It is recommended that you have the Kepler 4.3.2 version of
676 the Eclipse IDE installed on your development system. 676 the Eclipse IDE installed on your development system.
677 However, if you currently have the Juno 4.2 version 677 However, if you currently have the Juno 4.2 version
678 installed and you do not want to upgrade the IDE, you can 678 installed and you do not want to upgrade the IDE, you can
@@ -680,10 +680,10 @@
680 </para> 680 </para>
681 681
682 <para> 682 <para>
683 If you do not have the Kepler 4.3 Eclipse IDE installed, you 683 If you do not have the Kepler 4.3.2 Eclipse IDE installed,
684 can find the tarball at 684 you can find the tarball at
685 <ulink url='&ECLIPSE_MAIN_URL;'></ulink>. 685 <ulink url='&ECLIPSE_MAIN_URL;'></ulink>.
686 From that site, choose the Eclipse Standard 4.3 version 686 From that site, choose the Eclipse Standard 4.3.2 version
687 particular to your development host. 687 particular to your development host.
688 This version contains the Eclipse Platform, the Java 688 This version contains the Eclipse Platform, the Java
689 Development Tools (JDT), and the Plug-in Development 689 Development Tools (JDT), and the Plug-in Development
@@ -698,7 +698,7 @@
698 using the default name <filename>eclipse</filename>: 698 using the default name <filename>eclipse</filename>:
699 <literallayout class='monospaced'> 699 <literallayout class='monospaced'>
700 $ cd ~ 700 $ cd ~
701 $ tar -xzvf ~/Downloads/eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz 701 $ tar -xzvf ~/Downloads/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz
702 </literallayout> 702 </literallayout>
703 </para> 703 </para>
704 </section> 704 </section>
@@ -735,7 +735,7 @@
735 <listitem><para>Expand the box next to "Mobile and 735 <listitem><para>Expand the box next to "Mobile and
736 Device Development" and select the following boxes: 736 Device Development" and select the following boxes:
737 <itemizedlist> 737 <itemizedlist>
738 <listitem><para><filename>C/C++ Remote Launch</filename></para></listitem> 738 <listitem><para><filename>C/C++ Remote Launch (Requires RSE Remote System Explorer)</filename></para></listitem>
739 <listitem><para><filename>Remote System Explorer End-user Runtime</filename></para></listitem> 739 <listitem><para><filename>Remote System Explorer End-user Runtime</filename></para></listitem>
740 <listitem><para><filename>Remote System Explorer User Actions</filename></para></listitem> 740 <listitem><para><filename>Remote System Explorer User Actions</filename></para></listitem>
741 <listitem><para><filename>Target Management Terminal</filename></para></listitem> 741 <listitem><para><filename>Target Management Terminal</filename></para></listitem>
@@ -744,7 +744,7 @@
744 </itemizedlist></para></listitem> 744 </itemizedlist></para></listitem>
745 <listitem><para>Expand the box next to "Programming 745 <listitem><para>Expand the box next to "Programming
746 Languages" and select the 746 Languages" and select the
747 <filename>Autotools Support for CDT</filename> 747 <filename>C/C++ Autotools Support</filename>
748 and <filename>C/C++ Development Tools</filename> 748 and <filename>C/C++ Development Tools</filename>
749 boxes.</para></listitem> 749 boxes.</para></listitem>
750 <listitem><para>Complete the installation and restart 750 <listitem><para>Complete the installation and restart
@@ -871,7 +871,8 @@
871 <listitem><para>When the script finishes execution, 871 <listitem><para>When the script finishes execution,
872 it prompts you with instructions on how to run 872 it prompts you with instructions on how to run
873 the <filename>build.sh</filename> script, which 873 the <filename>build.sh</filename> script, which
874 is also in the <filename>scripts</filename> of 874 is also in the <filename>scripts</filename>
875 directory of
875 the Git repository created earlier. 876 the Git repository created earlier.
876 </para></listitem> 877 </para></listitem>
877 <listitem><para>Run the <filename>build.sh</filename> script 878 <listitem><para>Run the <filename>build.sh</filename> script
@@ -896,7 +897,7 @@
896 <listitem><para>Provide anything you want in the 897 <listitem><para>Provide anything you want in the
897 "Name" field.</para></listitem> 898 "Name" field.</para></listitem>
898 <listitem><para>Click "Archive" and browse to the 899 <listitem><para>Click "Archive" and browse to the
899 ZIP file you built in step seven. 900 ZIP file you built in step eight.
900 This ZIP file should not be "unzipped", and must 901 This ZIP file should not be "unzipped", and must
901 be the <filename>*archive.zip</filename> file 902 be the <filename>*archive.zip</filename> file
902 created by running the 903 created by running the
@@ -1016,7 +1017,7 @@
1016 If you used the ADT Installer script and 1017 If you used the ADT Installer script and
1017 accepted the default installation directory, 1018 accepted the default installation directory,
1018 then the location is 1019 then the location is
1019 <filename>/opt/poky/&lt;release&gt;</filename>. 1020 <filename>/opt/poky/&DISTRO;</filename>.
1020 Additionally, when you use the ADT Installer 1021 Additionally, when you use the ADT Installer
1021 script, the same location is used for the QEMU 1022 script, the same location is used for the QEMU
1022 user-space tools and the NFS boot process. 1023 user-space tools and the NFS boot process.
@@ -1031,7 +1032,9 @@
1031 <para>For information on how to install the 1032 <para>For information on how to install the
1032 toolchain and on how to extract and install the 1033 toolchain and on how to extract and install the
1033 sysroot filesystem, see the 1034 sysroot filesystem, see the
1034 "<ulink url='&YOCTO_DOCS_ADT_URL;#installing-the-adt'>Installing the ADT and Toolchains</ulink>" section. 1035 "<ulink url='&YOCTO_DOCS_ADT_URL;#installing-the-adt'>Installing the ADT and Toolchains</ulink>"
1036 section in the Yocto Project Application
1037 Developer's Guide.
1035 </para></listitem> 1038 </para></listitem>
1036 <listitem><para><emphasis>Select the Target Architecture:</emphasis> 1039 <listitem><para><emphasis>Select the Target Architecture:</emphasis>
1037 The target architecture is the type of hardware 1040 The target architecture is the type of hardware
@@ -1059,7 +1062,7 @@
1059 emulator, or you can choose to run your image on actual 1062 emulator, or you can choose to run your image on actual
1060 hardware. 1063 hardware.
1061 <itemizedlist> 1064 <itemizedlist>
1062 <listitem><para><emphasis><filename>QEMU:</filename></emphasis> 1065 <listitem><para><emphasis>QEMU:</emphasis>
1063 Select this option if you will be using the 1066 Select this option if you will be using the
1064 QEMU emulator. 1067 QEMU emulator.
1065 If you are using the emulator, you also need to 1068 If you are using the emulator, you also need to
@@ -1099,7 +1102,7 @@
1099 configuration in the 1102 configuration in the
1100 <filename>Sysroot Location:</filename> field. 1103 <filename>Sysroot Location:</filename> field.
1101 </para></listitem> 1104 </para></listitem>
1102 <listitem><para><emphasis><filename>External HW:</filename></emphasis> 1105 <listitem><para><emphasis>External HW:</emphasis>
1103 Select this option if you will be using actual 1106 Select this option if you will be using actual
1104 hardware.</para></listitem> 1107 hardware.</para></listitem>
1105 </itemizedlist> 1108 </itemizedlist>
@@ -1186,7 +1189,7 @@
1186 individual project.</para> 1189 individual project.</para>
1187 <para>By default, the Cross Compiler Options and Target 1190 <para>By default, the Cross Compiler Options and Target
1188 Options for a project are inherited from settings you 1191 Options for a project are inherited from settings you
1189 provide using the Preferences Dialog as described 1192 provided using the Preferences Dialog as described
1190 earlier in the 1193 earlier in the
1191 "<link linkend='configuring-the-eclipse-yocto-plug-in'>Configuring the Eclipse Yocto Plug-in</link>" section. 1194 "<link linkend='configuring-the-eclipse-yocto-plug-in'>Configuring the Eclipse Yocto Plug-in</link>" section.
1192 The Yocto Project Settings Dialog allows you to override 1195 The Yocto Project Settings Dialog allows you to override
@@ -1264,7 +1267,7 @@
1264 1267
1265 <para> 1268 <para>
1266 Once the QEMU emulator is running the image, you can deploy 1269 Once the QEMU emulator is running the image, you can deploy
1267 your application using the Eclipse IDE and use then use 1270 your application using the Eclipse IDE and then use
1268 the emulator to perform debugging. 1271 the emulator to perform debugging.
1269 Follow these steps to deploy the application. 1272 Follow these steps to deploy the application.
1270 <orderedlist> 1273 <orderedlist>
@@ -1349,7 +1352,7 @@
1349 <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/oprofileui/'></ulink>. 1352 <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/oprofileui/'></ulink>.
1350 You can also find more information on setting up and 1353 You can also find more information on setting up and
1351 using this tool in the 1354 using this tool in the
1352 "<ulink url='&YOCTO_DOCS_PROF_URL;#profile-manual-oprofile'>OProfile</ulink>" 1355 "<ulink url='&YOCTO_DOCS_PROF_URL;#profile-manual-oprofile'>oprofile</ulink>"
1353 section of the Yocto Project Profiling and Tracing 1356 section of the Yocto Project Profiling and Tracing
1354 Manual. 1357 Manual.
1355 <note>The <filename>oprofile-server</filename> is 1358 <note>The <filename>oprofile-server</filename> is