diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2015-04-28 14:25:01 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-05-03 11:49:35 +0100 |
commit | 7a8f37daa7b42905233c31366915b897886a957a (patch) | |
tree | 38d1b6e28a23b9b396087d4fa63cbe0972f49a9a | |
parent | b72cb0dbbe00d180e32245d0166ddb3f70b01681 (diff) | |
download | poky-7a8f37daa7b42905233c31366915b897886a957a.tar.gz |
dev-manual: Updates to add Luna support for Eclipse
Adding Luna and dropping Juno. Pretty much went through the
"Working With Eclipse" section and dropped Juno and added
Luna. A major deletion was the BitBake Commander section using
Hob. Todor told me to drop this section completely. Note that
I also added a couple new YoctoProjectTools that appear on the
menu: SystemTap and yocto-bsp.
(From yocto-docs rev: b63ec6c706f41dc4666c2fd79d797962c35f8baa)
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.xml | 361 |
1 files changed, 163 insertions, 198 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 255a814981..fd0d156494 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml | |||
@@ -668,8 +668,8 @@ | |||
668 | The Eclipse IDE is a popular development environment and it fully | 668 | The Eclipse IDE is a popular development environment and it fully |
669 | supports development using the Yocto Project. | 669 | supports development using the Yocto Project. |
670 | <note> | 670 | <note> |
671 | This release of the Yocto Project supports both the Kepler | 671 | This release of the Yocto Project supports both the Luna |
672 | and Juno versions of the Eclipse IDE. | 672 | and Kepler versions of the Eclipse IDE. |
673 | Thus, the following information provides setup information for | 673 | Thus, the following information provides setup information for |
674 | both versions. | 674 | both versions. |
675 | </note> | 675 | </note> |
@@ -722,19 +722,20 @@ | |||
722 | <title>Installing the Eclipse IDE</title> | 722 | <title>Installing the Eclipse IDE</title> |
723 | 723 | ||
724 | <para> | 724 | <para> |
725 | It is recommended that you have the Kepler 4.3.2 version of | 725 | It is recommended that you have the Luna SR2 (4.4.2) |
726 | the Eclipse IDE installed on your development system. | 726 | version of the Eclipse IDE installed on your development |
727 | However, if you currently have the Juno 4.2 version | 727 | system. |
728 | However, if you currently have the Kepler 4.3.2 version | ||
728 | installed and you do not want to upgrade the IDE, you can | 729 | installed and you do not want to upgrade the IDE, you can |
729 | configure Juno to work with the Yocto Project. | 730 | configure Kepler to work with the Yocto Project. |
730 | </para> | 731 | </para> |
731 | 732 | ||
732 | <para> | 733 | <para> |
733 | If you do not have the Kepler 4.3.2 Eclipse IDE installed, | 734 | If you do not have the Luna SR2 (4.4.2) Eclipse IDE |
734 | you can find the tarball at | 735 | installed, you can find the tarball at |
735 | <ulink url='&ECLIPSE_MAIN_URL;'></ulink>. | 736 | <ulink url='&ECLIPSE_MAIN_URL;'></ulink>. |
736 | From that site, choose the Eclipse Standard 4.3.2 version | 737 | From that site, choose the appropriate download from the |
737 | particular to your development host. | 738 | "Eclipse IDE for C/C++ Developers". |
738 | This version contains the Eclipse Platform, the Java | 739 | This version contains the Eclipse Platform, the Java |
739 | Development Tools (JDT), and the Plug-in Development | 740 | Development Tools (JDT), and the Plug-in Development |
740 | Environment. | 741 | Environment. |
@@ -748,7 +749,7 @@ | |||
748 | using the default name <filename>eclipse</filename>: | 749 | using the default name <filename>eclipse</filename>: |
749 | <literallayout class='monospaced'> | 750 | <literallayout class='monospaced'> |
750 | $ cd ~ | 751 | $ cd ~ |
751 | $ $ tar -xzvf ~/Downloads/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz | 752 | $ tar -xzvf ~/Downloads/eclipse-cpp-luna-SR2-linux-gtk-x86_64.tar.gz |
752 | </literallayout> | 753 | </literallayout> |
753 | </para> | 754 | </para> |
754 | </section> | 755 | </section> |
@@ -771,24 +772,37 @@ | |||
771 | select "Install New Software" from the "Help" | 772 | select "Install New Software" from the "Help" |
772 | pull-down menu.</para></listitem> | 773 | pull-down menu.</para></listitem> |
773 | <listitem><para>Select | 774 | <listitem><para>Select |
774 | <filename>Kepler - &ECLIPSE_KEPLER_URL;</filename> | 775 | <filename>Luna - &ECLIPSE_LUNA_URL;</filename> |
775 | from the "Work with:" pull-down menu. | 776 | from the "Work with:" pull-down menu. |
776 | <note> | 777 | <note> |
777 | For Juno, select | 778 | For Kepler, select |
778 | <filename>Juno - &ECLIPSE_JUNO_URL;</filename> | 779 | <filename>Kepler - &ECLIPSE_KEPLER_URL;</filename> |
779 | </note> | 780 | </note> |
780 | </para></listitem> | 781 | </para></listitem> |
781 | <listitem><para>Expand the box next to "Linux Tools" | 782 | <listitem><para>Expand the box next to "Linux Tools" |
782 | and select the | 783 | and select the |
783 | <filename>LTTng - Linux Tracing Toolkit</filename> | 784 | <filename>Linux Tools LTTng Tracer Control</filename>, |
784 | boxes.</para></listitem> | 785 | <filename>Linux Tools LTTng Userspace Analysis</filename>, |
786 | and | ||
787 | <filename>LTTng Kernel Analysis</filename> boxes. | ||
788 | If these selections do not appear in the list, | ||
789 | that means the items are already installed. | ||
790 | <note> | ||
791 | For Kepler, select | ||
792 | <filename>LTTng - Linux Tracing Toolkit</filename> | ||
793 | box. | ||
794 | </note> | ||
795 | </para></listitem> | ||
785 | <listitem><para>Expand the box next to "Mobile and | 796 | <listitem><para>Expand the box next to "Mobile and |
786 | Device Development" and select the following boxes: | 797 | Device Development" and select the following boxes. |
798 | Again, if any of the following items are not | ||
799 | available for selection, that means the items are | ||
800 | already installed: | ||
787 | <itemizedlist> | 801 | <itemizedlist> |
788 | <listitem><para><filename>C/C++ Remote Launch (Requires RSE Remote System Explorer)</filename></para></listitem> | 802 | <listitem><para><filename>C/C++ Remote Launch (Requires RSE Remote System Explorer)</filename></para></listitem> |
789 | <listitem><para><filename>Remote System Explorer End-user Runtime</filename></para></listitem> | 803 | <listitem><para><filename>Remote System Explorer End-user Runtime</filename></para></listitem> |
790 | <listitem><para><filename>Remote System Explorer User Actions</filename></para></listitem> | 804 | <listitem><para><filename>Remote System Explorer User Actions</filename></para></listitem> |
791 | <listitem><para><filename>Target Management Terminal</filename></para></listitem> | 805 | <listitem><para><filename>Target Management Terminal (Core SDK)</filename></para></listitem> |
792 | <listitem><para><filename>TCF Remote System Explorer add-in</filename></para></listitem> | 806 | <listitem><para><filename>TCF Remote System Explorer add-in</filename></para></listitem> |
793 | <listitem><para><filename>TCF Target Explorer</filename></para></listitem> | 807 | <listitem><para><filename>TCF Target Explorer</filename></para></listitem> |
794 | </itemizedlist></para></listitem> | 808 | </itemizedlist></para></listitem> |
@@ -796,7 +810,10 @@ | |||
796 | Languages" and select the | 810 | Languages" and select the |
797 | <filename>C/C++ Autotools Support</filename> | 811 | <filename>C/C++ Autotools Support</filename> |
798 | and <filename>C/C++ Development Tools</filename> | 812 | and <filename>C/C++ Development Tools</filename> |
799 | boxes.</para></listitem> | 813 | boxes. |
814 | For Luna, these items do not appear on the list | ||
815 | as they are already installed. | ||
816 | </para></listitem> | ||
800 | <listitem><para>Complete the installation and restart | 817 | <listitem><para>Complete the installation and restart |
801 | the Eclipse IDE.</para></listitem> | 818 | the Eclipse IDE.</para></listitem> |
802 | </orderedlist> | 819 | </orderedlist> |
@@ -828,12 +845,12 @@ | |||
828 | <listitem><para>Click "Add..." in the "Work with:" | 845 | <listitem><para>Click "Add..." in the "Work with:" |
829 | area.</para></listitem> | 846 | area.</para></listitem> |
830 | <listitem><para>Enter | 847 | <listitem><para>Enter |
831 | <filename>&ECLIPSE_DL_PLUGIN_URL;/kepler</filename> | 848 | <filename>&ECLIPSE_DL_PLUGIN_URL;/luna</filename> |
832 | in the URL field and provide a meaningful name | 849 | in the URL field and provide a meaningful name |
833 | in the "Name" field. | 850 | in the "Name" field. |
834 | <note> | 851 | <note> |
835 | If you are using Juno, use | 852 | If you are using Kepler, use |
836 | <filename>&ECLIPSE_DL_PLUGIN_URL;/juno</filename> | 853 | <filename>&ECLIPSE_DL_PLUGIN_URL;/kepler</filename> |
837 | in the URL field. | 854 | in the URL field. |
838 | </note></para></listitem> | 855 | </note></para></listitem> |
839 | <listitem><para>Click "OK" to have the entry added | 856 | <listitem><para>Click "OK" to have the entry added |
@@ -851,6 +868,11 @@ | |||
851 | <listitem><para>Complete the remaining software | 868 | <listitem><para>Complete the remaining software |
852 | installation steps and then restart the Eclipse | 869 | installation steps and then restart the Eclipse |
853 | IDE to finish the installation of the plug-in. | 870 | IDE to finish the installation of the plug-in. |
871 | <note> | ||
872 | You can click "OK" when prompted about | ||
873 | installing software that contains unsigned | ||
874 | content. | ||
875 | </note> | ||
854 | </para></listitem> | 876 | </para></listitem> |
855 | </orderedlist> | 877 | </orderedlist> |
856 | </para> | 878 | </para> |
@@ -870,17 +892,25 @@ | |||
870 | <listitem><para>Use the Oracle JDK. | 892 | <listitem><para>Use the Oracle JDK. |
871 | If you don't have that, go to | 893 | If you don't have that, go to |
872 | <ulink url='http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html'></ulink> | 894 | <ulink url='http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html'></ulink> |
873 | and download the appropriate tarball | 895 | and download the latest appropriate |
874 | for your development system and | 896 | Java SE Development Kit tarball for |
897 | your development system and | ||
875 | extract it into your home directory. | 898 | extract it into your home directory. |
876 | </para></listitem> | 899 | </para></listitem> |
877 | <listitem><para>In the shell you are going | 900 | <listitem><para>In the shell you are going |
878 | to do your work, export the location of | 901 | to do your work, export the location of |
879 | the Oracle Java as follows: | 902 | the Oracle Java. |
903 | The previous step creates a new folder | ||
904 | for the extracted software. | ||
905 | You need to use the following | ||
906 | <filename>export</filename> command | ||
907 | and provide the specific location: | ||
880 | <literallayout class='monospaced'> | 908 | <literallayout class='monospaced'> |
881 | export PATH=~/jdk1.7.0_40/bin:$PATH | 909 | export PATH=~/<replaceable>extracted_jdk_location</replaceable>/bin:$PATH |
882 | </literallayout></para></listitem> | 910 | </literallayout> |
883 | </orderedlist></para></listitem> | 911 | </para></listitem> |
912 | </orderedlist> | ||
913 | </para></listitem> | ||
884 | <listitem><para>In the same shell, create a Git | 914 | <listitem><para>In the same shell, create a Git |
885 | repository with: | 915 | repository with: |
886 | <literallayout class='monospaced'> | 916 | <literallayout class='monospaced'> |
@@ -888,53 +918,69 @@ | |||
888 | $ git clone git://git.yoctoproject.org/eclipse-poky | 918 | $ git clone git://git.yoctoproject.org/eclipse-poky |
889 | </literallayout> | 919 | </literallayout> |
890 | </para></listitem> | 920 | </para></listitem> |
891 | <listitem><para>Be sure to checkout the specific | 921 | <listitem><para>Be sure to checkout the correct |
892 | plug-in branch. | 922 | tag. |
893 | For example, if you are using Kepler, do the | 923 | For example, if you are using Luna, do the |
894 | following: | 924 | following: |
895 | <literallayout class='monospaced'> | 925 | <literallayout class='monospaced'> |
896 | $ git checkout kepler | 926 | $ git checkout luna/yocto-1.8 |
897 | </literallayout> | 927 | </literallayout> |
928 | This puts you in a detached HEAD state, which | ||
929 | is fine since you are only going to be building | ||
930 | and not developing. | ||
931 | <note> | ||
932 | If you are building kepler, checkout the | ||
933 | <filename>kepler/yocto-1.8</filename> | ||
934 | branch. | ||
935 | </note> | ||
898 | </para></listitem> | 936 | </para></listitem> |
899 | <listitem><para>Change to the | 937 | <listitem><para>Change to the |
900 | <filename>scripts</filename> | 938 | <filename>scripts</filename> |
901 | directory within the Git repository: | 939 | directory within the Git repository: |
902 | <literallayout class='monospaced'> | 940 | <literallayout class='monospaced'> |
903 | $ cd scripts | 941 | $ cd scripts |
904 | </literallayout></para></listitem> | 942 | </literallayout> |
943 | </para></listitem> | ||
905 | <listitem><para>Set up the local build environment | 944 | <listitem><para>Set up the local build environment |
906 | by running the setup script: | 945 | by running the setup script: |
907 | <literallayout class='monospaced'> | 946 | <literallayout class='monospaced'> |
908 | $ ./setup.sh | 947 | $ ./setup.sh |
909 | </literallayout></para></listitem> | 948 | </literallayout> |
949 | </para></listitem> | ||
910 | <listitem><para>When the script finishes execution, | 950 | <listitem><para>When the script finishes execution, |
911 | it prompts you with instructions on how to run | 951 | it prompts you with instructions on how to run |
912 | the <filename>build.sh</filename> script, which | 952 | the <filename>build.sh</filename> script, which |
913 | is also in the <filename>scripts</filename> | 953 | is also in the <filename>scripts</filename> |
914 | directory of | 954 | directory of the Git repository created |
915 | the Git repository created earlier. | 955 | earlier. |
916 | </para></listitem> | 956 | </para></listitem> |
917 | <listitem><para>Run the <filename>build.sh</filename> script | 957 | <listitem><para>Run the <filename>build.sh</filename> |
918 | as directed. | 958 | script as directed. |
919 | Be sure to provide the name of the Git branch | 959 | Be sure to provide the tag name, documentation |
920 | along with the Yocto Project release you are | 960 | branch, and a release name. |
921 | using. | ||
922 | Here is an example that uses the | 961 | Here is an example that uses the |
923 | <filename>&DISTRO_NAME;</filename> branch: | 962 | <filename>luna/yocto-1.8</filename> tag, the |
963 | <filename>master</filename> documentation | ||
964 | branch, and | ||
965 | <filename>&DISTRO_NAME;</filename> for the | ||
966 | release name: | ||
924 | <literallayout class='monospaced'> | 967 | <literallayout class='monospaced'> |
925 | $ ECLIPSE_HOME=/home/scottrif/eclipse-poky/scripts/eclipse ./build.sh &DISTRO_NAME; &DISTRO_NAME; | 968 | $ ECLIPSE_HOME=/home/scottrif/eclipse-poky/scripts/eclipse ./build.sh luna/yocto-1.8 master &DISTRO_NAME; 2>&1 | tee -a build.log |
926 | </literallayout> | 969 | </literallayout> |
927 | After running the script, the file | 970 | After running the script, the file |
928 | <filename>org.yocto.sdk-</filename><replaceable>release</replaceable><filename>-</filename><replaceable>date</replaceable><filename>-archive.zip</filename> | 971 | <filename>org.yocto.sdk-</filename><replaceable>release</replaceable><filename>-</filename><replaceable>date</replaceable><filename>-archive.zip</filename> |
929 | is in the current directory.</para></listitem> | 972 | is in the current directory. |
973 | </para></listitem> | ||
930 | <listitem><para>If necessary, start the Eclipse IDE | 974 | <listitem><para>If necessary, start the Eclipse IDE |
931 | and be sure you are in the Workbench. | 975 | and be sure you are in the Workbench. |
932 | </para></listitem> | 976 | </para></listitem> |
933 | <listitem><para>Select "Install New Software" from the "Help" pull-down menu. | 977 | <listitem><para>Select "Install New Software" from |
978 | the "Help" pull-down menu. | ||
934 | </para></listitem> | 979 | </para></listitem> |
935 | <listitem><para>Click "Add".</para></listitem> | 980 | <listitem><para>Click "Add".</para></listitem> |
936 | <listitem><para>Provide anything you want in the | 981 | <listitem><para>Provide anything you want in the |
937 | "Name" field.</para></listitem> | 982 | "Name" field. |
983 | </para></listitem> | ||
938 | <listitem><para>Click "Archive" and browse to the | 984 | <listitem><para>Click "Archive" and browse to the |
939 | ZIP file you built in step eight. | 985 | ZIP file you built in step eight. |
940 | This ZIP file should not be "unzipped", and must | 986 | This ZIP file should not be "unzipped", and must |
@@ -942,13 +988,24 @@ | |||
942 | created by running the | 988 | created by running the |
943 | <filename>build.sh</filename> script. | 989 | <filename>build.sh</filename> script. |
944 | </para></listitem> | 990 | </para></listitem> |
945 | <listitem><para>Click through the "Okay" buttons. | 991 | <listitem><para>Click the "OK" button. |
992 | </para></listitem> | ||
993 | <listitem><para>Check the boxes that appear in | ||
994 | the installation window to install the | ||
995 | <filename>Yocto Project ADT Plug-in</filename>, | ||
996 | <filename>Yocto Project Bitbake Commander Plug-in</filename>, | ||
997 | and the | ||
998 | <filename>Yocto Project Documentation plug-in</filename>. | ||
999 | </para></listitem> | ||
1000 | <listitem><para>Finish the installation by clicking | ||
1001 | through the appropriate buttons. | ||
1002 | You can click "OK" when prompted about | ||
1003 | installing software that contains unsigned | ||
1004 | content. | ||
946 | </para></listitem> | 1005 | </para></listitem> |
947 | <listitem><para>Check the boxes | ||
948 | in the installation window and complete | ||
949 | the installation.</para></listitem> | ||
950 | <listitem><para>Restart the Eclipse IDE if | 1006 | <listitem><para>Restart the Eclipse IDE if |
951 | necessary.</para></listitem> | 1007 | necessary. |
1008 | </para></listitem> | ||
952 | </orderedlist> | 1009 | </orderedlist> |
953 | </para> | 1010 | </para> |
954 | 1011 | ||
@@ -977,9 +1034,10 @@ | |||
977 | Eclipse IDE: | 1034 | Eclipse IDE: |
978 | <itemizedlist> | 1035 | <itemizedlist> |
979 | <listitem><para>Choose "Preferences" from the | 1036 | <listitem><para>Choose "Preferences" from the |
980 | "Windows" menu to display the Preferences Dialog. | 1037 | "Window" menu to display the Preferences Dialog. |
981 | </para></listitem> | 1038 | </para></listitem> |
982 | <listitem><para>Click "Yocto Project ADT". | 1039 | <listitem><para>Click "Yocto Project ADT" to display |
1040 | the configuration screen. | ||
983 | </para></listitem> | 1041 | </para></listitem> |
984 | </itemizedlist> | 1042 | </itemizedlist> |
985 | </para> | 1043 | </para> |
@@ -1055,10 +1113,13 @@ | |||
1055 | the target hardware resides. | 1113 | the target hardware resides. |
1056 | If you used the ADT Installer script and | 1114 | If you used the ADT Installer script and |
1057 | accepted the default installation directory, | 1115 | accepted the default installation directory, |
1058 | then the location is | 1116 | then the location in your home directory |
1059 | <filename>/opt/poky/&DISTRO;/sysroots</filename>. | 1117 | in a folder named |
1118 | <filename>test-yocto/</filename><replaceable>target_arch</replaceable>. | ||
1060 | Additionally, when you use the ADT Installer | 1119 | Additionally, when you use the ADT Installer |
1061 | script, the same location is used for the QEMU | 1120 | script, the |
1121 | <filename>/opt/poky/&DISTRO;/sysroots</filename> | ||
1122 | location is used for the QEMU | ||
1062 | user-space tools and the NFS boot process. | 1123 | user-space tools and the NFS boot process. |
1063 | </para> | 1124 | </para> |
1064 | <para>If you used either of the other two | 1125 | <para>If you used either of the other two |
@@ -1183,7 +1244,7 @@ | |||
1183 | </para></listitem> | 1244 | </para></listitem> |
1184 | <listitem><para>Double click <filename>C Project</filename> | 1245 | <listitem><para>Double click <filename>C Project</filename> |
1185 | to create the project.</para></listitem> | 1246 | to create the project.</para></listitem> |
1186 | <listitem><para>Expand <filename>Yocto Project ADT Project</filename>. | 1247 | <listitem><para>Expand <filename>Yocto Project ADT Autotools Project</filename>. |
1187 | </para></listitem> | 1248 | </para></listitem> |
1188 | <listitem><para>Select <filename>Hello World ANSI C Autotools Project</filename>. | 1249 | <listitem><para>Select <filename>Hello World ANSI C Autotools Project</filename>. |
1189 | This is an Autotools-based project based on a Yocto | 1250 | This is an Autotools-based project based on a Yocto |
@@ -1236,14 +1297,9 @@ | |||
1236 | </para></listitem> | 1297 | </para></listitem> |
1237 | <listitem><para>Make your configurations for the project | 1298 | <listitem><para>Make your configurations for the project |
1238 | and click "OK". | 1299 | and click "OK". |
1239 | If you are running the Juno version of Eclipse, you can | ||
1240 | skip down to the next section where you build the | ||
1241 | project. | ||
1242 | If you are not working with Juno, you need to reconfigure the | ||
1243 | project as described in the next step. | ||
1244 | </para></listitem> | 1300 | </para></listitem> |
1245 | <listitem><para>Select "Reconfigure Project" from the | 1301 | <listitem><para>Right-click in the navigation pane and |
1246 | "Project" menu. | 1302 | select "Reconfigure Project" from the pop-up menu. |
1247 | This selection reconfigures the project by running | 1303 | This selection reconfigures the project by running |
1248 | <filename>autogen.sh</filename> in the workspace for | 1304 | <filename>autogen.sh</filename> in the workspace for |
1249 | your project. | 1305 | your project. |
@@ -1264,9 +1320,7 @@ | |||
1264 | <title>Building the Project</title> | 1320 | <title>Building the Project</title> |
1265 | 1321 | ||
1266 | <para> | 1322 | <para> |
1267 | To build the project in Juno, right click on the project in | 1323 | To build the project select "Build Project" from the |
1268 | the navigator pane and select "Build Project". | ||
1269 | If you are not running Juno, select "Build Project" from the | ||
1270 | "Project" menu. | 1324 | "Project" menu. |
1271 | The console should update and you can note the cross-compiler | 1325 | The console should update and you can note the cross-compiler |
1272 | you are using. | 1326 | you are using. |
@@ -1290,7 +1344,8 @@ | |||
1290 | Your image should appear as a selectable menu item. | 1344 | Your image should appear as a selectable menu item. |
1291 | </para></listitem> | 1345 | </para></listitem> |
1292 | <listitem><para>Select your image from the menu to launch | 1346 | <listitem><para>Select your image from the menu to launch |
1293 | the emulator in a new window.</para></listitem> | 1347 | the emulator in a new window. |
1348 | </para></listitem> | ||
1294 | <listitem><para>If needed, enter your host root password in | 1349 | <listitem><para>If needed, enter your host root password in |
1295 | the shell window at the prompt. | 1350 | the shell window at the prompt. |
1296 | This sets up a <filename>Tap 0</filename> connection | 1351 | This sets up a <filename>Tap 0</filename> connection |
@@ -1299,9 +1354,10 @@ | |||
1299 | <listitem><para>Wait for QEMU to launch.</para></listitem> | 1354 | <listitem><para>Wait for QEMU to launch.</para></listitem> |
1300 | <listitem><para>Once QEMU launches, you can begin operating | 1355 | <listitem><para>Once QEMU launches, you can begin operating |
1301 | within that environment. | 1356 | within that environment. |
1302 | For example, you could determine the IP Address | 1357 | One useful task at this point would be to determine the |
1303 | for the user-space NFS by using the | 1358 | IP Address for the user-space NFS by using the |
1304 | <filename>ifconfig</filename> command.</para></listitem> | 1359 | <filename>ifconfig</filename> command. |
1360 | </para></listitem> | ||
1305 | </orderedlist> | 1361 | </orderedlist> |
1306 | </para> | 1362 | </para> |
1307 | </section> | 1363 | </section> |
@@ -1345,7 +1401,7 @@ | |||
1345 | <listitem><para>Use the drop-down menu now in the | 1401 | <listitem><para>Use the drop-down menu now in the |
1346 | "Connection" field and pick the IP Address you entered. | 1402 | "Connection" field and pick the IP Address you entered. |
1347 | </para></listitem> | 1403 | </para></listitem> |
1348 | <listitem><para>Click "Run" to bring up a login screen | 1404 | <listitem><para>Click "Debug" to bring up a login screen |
1349 | and login.</para></listitem> | 1405 | and login.</para></listitem> |
1350 | <listitem><para>Accept the debug perspective. | 1406 | <listitem><para>Accept the debug perspective. |
1351 | </para></listitem> | 1407 | </para></listitem> |
@@ -1362,7 +1418,7 @@ | |||
1362 | These tools are aids in developing and debugging applications | 1418 | These tools are aids in developing and debugging applications |
1363 | and images. | 1419 | and images. |
1364 | You can run these user-space tools from within the Eclipse | 1420 | You can run these user-space tools from within the Eclipse |
1365 | IDE through the "YoctoTools" menu. | 1421 | IDE through the "YoctoProjectTools" menu. |
1366 | </para> | 1422 | </para> |
1367 | 1423 | ||
1368 | <para> | 1424 | <para> |
@@ -1403,7 +1459,7 @@ | |||
1403 | installed by default on the | 1459 | installed by default on the |
1404 | <filename>core-image-sato-sdk</filename> image.</note> | 1460 | <filename>core-image-sato-sdk</filename> image.</note> |
1405 | </para></listitem> | 1461 | </para></listitem> |
1406 | <listitem><para><emphasis><filename>Lttng2.0 ust trace import</filename>:</emphasis> | 1462 | <listitem><para><emphasis><filename>Lttng2.0 trace import</filename>:</emphasis> |
1407 | Selecting this tool transfers the remote target's | 1463 | Selecting this tool transfers the remote target's |
1408 | <filename>Lttng</filename> tracing data back to the | 1464 | <filename>Lttng</filename> tracing data back to the |
1409 | local host machine and uses the Lttng Eclipse plug-in | 1465 | local host machine and uses the Lttng Eclipse plug-in |
@@ -1420,13 +1476,15 @@ | |||
1420 | This tool no longer has any upstream support.</note> | 1476 | This tool no longer has any upstream support.</note> |
1421 | </para> | 1477 | </para> |
1422 | <para>Before you use the | 1478 | <para>Before you use the |
1423 | <filename>Lttng2.0 ust trace import</filename> tool, | 1479 | <filename>Lttng2.0 trace import</filename> tool, |
1424 | you need to setup the Lttng Eclipse plug-in and create a | 1480 | you need to setup the Lttng Eclipse plug-in and create a |
1425 | Tracing project. | 1481 | Tracing project. |
1426 | Do the following: | 1482 | Do the following: |
1427 | <orderedlist> | 1483 | <orderedlist> |
1428 | <listitem><para>Select "Open Perspective" from the | 1484 | <listitem><para>Select "Open Perspective" from the |
1429 | "Window" menu and then select "Tracing". | 1485 | "Window" menu and then select "Other..." to |
1486 | bring up a menu of other perspectives. | ||
1487 | Choose "Tracing". | ||
1430 | </para></listitem> | 1488 | </para></listitem> |
1431 | <listitem><para>Click "OK" to change the Eclipse | 1489 | <listitem><para>Click "OK" to change the Eclipse |
1432 | perspective into the Tracing perspective. | 1490 | perspective into the Tracing perspective. |
@@ -1435,11 +1493,14 @@ | |||
1435 | selecting "Project" from the "File -> New" menu. | 1493 | selecting "Project" from the "File -> New" menu. |
1436 | </para></listitem> | 1494 | </para></listitem> |
1437 | <listitem><para>Choose "Tracing Project" from the | 1495 | <listitem><para>Choose "Tracing Project" from the |
1438 | "Tracing" menu. | 1496 | "Tracing" menu and click "Next". |
1497 | </para></listitem> | ||
1498 | <listitem><para>Provide a name for your tracing | ||
1499 | project and click "Finish". | ||
1439 | </para></listitem> | 1500 | </para></listitem> |
1440 | <listitem><para>Generate your tracing data on the | 1501 | <listitem><para>Generate your tracing data on the |
1441 | remote target.</para></listitem> | 1502 | remote target.</para></listitem> |
1442 | <listitem><para>Select "Lttng2.0 ust trace import" | 1503 | <listitem><para>Select "Lttng2.0 trace import" |
1443 | from the "Yocto Project Tools" menu to | 1504 | from the "Yocto Project Tools" menu to |
1444 | start the data import process.</para></listitem> | 1505 | start the data import process.</para></listitem> |
1445 | <listitem><para>Specify your remote connection name. | 1506 | <listitem><para>Specify your remote connection name. |
@@ -1487,129 +1548,33 @@ | |||
1487 | section in the Yocto Project Profiling and Tracing | 1548 | section in the Yocto Project Profiling and Tracing |
1488 | Manual. | 1549 | Manual. |
1489 | </para></listitem> | 1550 | </para></listitem> |
1551 | <listitem><para><emphasis><filename>SystemTap</filename>:</emphasis> | ||
1552 | Systemtap is a tool that lets you create and reuse | ||
1553 | scripts to examine the activities of a live Linux | ||
1554 | system. | ||
1555 | You can easily extract, filter, and summarize data | ||
1556 | that helps you diagnose complex performance or | ||
1557 | functional problems. | ||
1558 | For more information on setting up and using | ||
1559 | <filename>SystemTap</filename>, see the | ||
1560 | <ulink url='https://sourceware.org/systemtap/documentation.html'>SystemTap Documentation</ulink>. | ||
1561 | </para></listitem> | ||
1562 | <listitem><para><emphasis><filename>yocto-bsp</filename>:</emphasis> | ||
1563 | The <filename>yocto-bsp</filename> tool lets you | ||
1564 | quickly set up a Board Support Package (BSP) layer. | ||
1565 | The tool requires a Metadata location, build location, | ||
1566 | BSP name, BSP output location, and a kernel | ||
1567 | architecture. | ||
1568 | For more information on the | ||
1569 | <filename>yocto-bsp</filename> tool outside of Eclipse, | ||
1570 | see the | ||
1571 | "<ulink url='&YOCTO_DOCS_BSP_URL;#creating-a-new-bsp-layer-using-the-yocto-bsp-script'>Creating a new BSP Layer Using the yocto-bsp Script</ulink>" | ||
1572 | section in the Yocto Project Board Support Package | ||
1573 | (BSP) Developer's Guide. | ||
1574 | </para></listitem> | ||
1490 | </itemizedlist> | 1575 | </itemizedlist> |
1491 | </para> | 1576 | </para> |
1492 | </section> | 1577 | </section> |
1493 | |||
1494 | <section id='customizing-an-image-using-a-bitbake-commander-project-and-hob'> | ||
1495 | <title>Customizing an Image Using a BitBake Commander Project and Hob</title> | ||
1496 | |||
1497 | <para> | ||
1498 | Within the Eclipse IDE, you can create a Yocto BitBake Commander | ||
1499 | project, edit the <link linkend='metadata'>Metadata</link>, and | ||
1500 | then use | ||
1501 | <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'>Hob</ulink> to build a customized image all within one IDE. | ||
1502 | </para> | ||
1503 | |||
1504 | <section id='creating-the-yocto-bitbake-commander-project'> | ||
1505 | <title>Creating the Yocto BitBake Commander Project</title> | ||
1506 | |||
1507 | <para> | ||
1508 | To create a Yocto BitBake Commander project, follow these | ||
1509 | steps: | ||
1510 | <orderedlist> | ||
1511 | <listitem><para>Select "Other" from the | ||
1512 | "Window -> Open Perspective" menu | ||
1513 | and then choose "Bitbake Commander". | ||
1514 | </para></listitem> | ||
1515 | <listitem><para>Click "OK" to change the perspective to | ||
1516 | Bitbake Commander.</para></listitem> | ||
1517 | <listitem><para>Select "Project" from the "File -> New" | ||
1518 | menu to create a new Yocto | ||
1519 | Bitbake Commander project.</para></listitem> | ||
1520 | <listitem><para>Choose "New Yocto Project" from the | ||
1521 | "Yocto Project Bitbake Commander" menu and click | ||
1522 | "Next".</para></listitem> | ||
1523 | <listitem><para>Enter the Project Name and choose the | ||
1524 | Project Location. | ||
1525 | The Yocto project's Metadata files will be put under | ||
1526 | the directory | ||
1527 | <filename><replaceable>project_location</replaceable>/<replaceable>project_name</replaceable></filename>. | ||
1528 | If that directory does not exist, you need to check | ||
1529 | the "Clone from Yocto Git Repository" box, which | ||
1530 | would execute a <filename>git clone</filename> | ||
1531 | command to get the project's Metadata files. | ||
1532 | <note> | ||
1533 | Do not specify your BitBake Commander project | ||
1534 | location as your Eclipse workspace. | ||
1535 | Doing so causes an error indicating that the | ||
1536 | current project overlaps the location of | ||
1537 | another project. | ||
1538 | This error occurs even if no such project exits. | ||
1539 | </note></para></listitem> | ||
1540 | <listitem><para>Select <filename>Finish</filename> to | ||
1541 | create the project.</para></listitem> | ||
1542 | </orderedlist> | ||
1543 | </para> | ||
1544 | </section> | ||
1545 | |||
1546 | <section id='editing-the-metadata'> | ||
1547 | <title>Editing the Metadata</title> | ||
1548 | |||
1549 | <para> | ||
1550 | After you create the Yocto Bitbake Commander project, you | ||
1551 | can modify the <link linkend='metadata'>Metadata</link> | ||
1552 | files by opening them in the project. | ||
1553 | When editing recipe files (<filename>.bb</filename> files), | ||
1554 | you can view BitBake variable values and information by | ||
1555 | hovering the mouse pointer over the variable name and | ||
1556 | waiting a few seconds. | ||
1557 | </para> | ||
1558 | |||
1559 | <para> | ||
1560 | To edit the Metadata, follow these steps: | ||
1561 | <orderedlist> | ||
1562 | <listitem><para>Select your Yocto Bitbake Commander | ||
1563 | project.</para></listitem> | ||
1564 | <listitem><para>Select "BitBake Recipe" from the | ||
1565 | "File -> New -> Yocto BitBake Commander" menu | ||
1566 | to open a new recipe wizard.</para></listitem> | ||
1567 | <listitem><para>Point to your source by filling in the | ||
1568 | "SRC_URL" field. | ||
1569 | For example, you can add a recipe to your | ||
1570 | <link linkend='source-directory'>Source Directory</link> | ||
1571 | by defining "SRC_URL" as follows: | ||
1572 | <literallayout class='monospaced'> | ||
1573 | ftp://ftp.gnu.org/gnu/m4/m4-1.4.9.tar.gz | ||
1574 | </literallayout></para></listitem> | ||
1575 | <listitem><para>Click "Populate" to calculate the | ||
1576 | archive md5, sha256, license checksum values and to | ||
1577 | auto-generate the recipe filename.</para></listitem> | ||
1578 | <listitem><para>Fill in the "Description" field. | ||
1579 | </para></listitem> | ||
1580 | <listitem><para>Be sure values for all required | ||
1581 | fields exist.</para></listitem> | ||
1582 | <listitem><para>Click "Finish".</para></listitem> | ||
1583 | </orderedlist> | ||
1584 | </para> | ||
1585 | </section> | ||
1586 | |||
1587 | <section id='biding-and-customizing-the-image-using-hob'> | ||
1588 | <title>Building and Customizing the Image Using Hob</title> | ||
1589 | |||
1590 | <para> | ||
1591 | To build and customize the image using Hob from within the | ||
1592 | Eclipse IDE, follow these steps: | ||
1593 | <orderedlist> | ||
1594 | <listitem><para>Select your Yocto Bitbake Commander | ||
1595 | project.</para></listitem> | ||
1596 | <listitem><para>Select "Launch Hob" from the "Project" | ||
1597 | menu.</para></listitem> | ||
1598 | <listitem><para>Enter the | ||
1599 | <link linkend='build-directory'>Build Directory</link> | ||
1600 | where you want to put your final images. | ||
1601 | </para></listitem> | ||
1602 | <listitem><para>Click "OK" to launch Hob. | ||
1603 | </para></listitem> | ||
1604 | <listitem><para>Use Hob to customize and build your own | ||
1605 | images. | ||
1606 | For information on Hob, see the | ||
1607 | <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'>Hob Project Page</ulink> | ||
1608 | on the Yocto Project website.</para></listitem> | ||
1609 | </orderedlist> | ||
1610 | </para> | ||
1611 | </section> | ||
1612 | </section> | ||
1613 | </section> | 1578 | </section> |
1614 | 1579 | ||
1615 | <section id='workflow-using-stand-alone-cross-development-toolchains'> | 1580 | <section id='workflow-using-stand-alone-cross-development-toolchains'> |