Differences

This shows you the differences between two versions of the page.

--- en:general_information:eclipse [2014/10/22 13:16] – liedmann
+++ en:general_information:eclipse [2019/09/23 11:14] – revised proper usage of the "Arm" trademark lenz
@@ Line 8: / Line 8: @@
   * Eclipse Indigo
   * CDT 8.0
-  * TQMa28 with i.MX28 (ARM9)
+  * TQMa28 with i.MX28 (1 x Arm926EJ-S<sup>(tm)</sup>)
-  * TQMa35 with i.MX35 (ARM11)
+  * TQMa35 with i.MX35 (1 x Arm1136JF-S<sup>(tm)</sup>)
   * LTIB 9.1.1
   * ELDK 4.2
@@ Line 21: / Line 21: @@
 http://www.Eclipse.org/cdt/downloads.php
+If you follow on this page the link to the desired Eclipse package (Eclipse CDT 8.0 for Indigo), there is a download link for the different architectures in the right column.
+Alternatively, you can directly go to http://www.Eclipse.org/downloads/. There you will find the same overview of available packages. After selecting "Linux" on top right, you can download the package
+**Eclipse IDE for C/C++ Linux Developers (includes Incubating components)**
+The executable Eclipse is in the extracted folder. No plugins have to be installed. Sometimes it may happen, however, that a Java runtime environment is required to execute Eclipse. This is installed with the following command:
+<code bash>
+user@ubuntu:~$ sudo apt-get install default-jre
+</code>
+==== Installation using apt-get ====
+The Eclipse platform is installed with apt-get:
+<code bash>
+user@ubuntu:~$ sudo apt-get install Eclipse-platform
+</code>
+<WRAP round important>
+Ubuntu 10.04 supplies the very old Eclipse Galileo. It is recommended to dirctly download a newer packet. See [[Eclipse#download_complete_package]]
+</WRAP>
+<WRAP round tip>
+The package Eclipse-platform only contains the platform and no language-specific plugins. These must be installed separately using the plugin manager. An existing installation of Eclipse can be used as well.
+</WRAP>
+===== Configuration =====
+**Workspace**: A workspace has to be created after Eclipse is launched. The workspace is in a folder in the file system. Projects can easily be referenced within the workspace. Different workspaces are primarily useful for different programs or for different purposes (e.g., a workspace for embedded projects, a workspace for web development, a workspace for Java projects).
+**Environment**:
+<WRAP round important>
+Starting Eclipse by double clicking in the file explorer does not take on the environment variables of the shell.
+</WRAP>
+The first way to use Eclipse with the environment variables is to start Eclipse from the console.
+Another option is to write the relevant environment variables to a file, e.g.,
+<code bash>
+user@ubuntu:~$ echo 'PATH=$PATH:/opt/eldk/usr/bin:/opt/eldk/bin
+export CROSS_COMPILE=arm-linux-' > setup_tqma28
+</code>
+and then to write a shell script that first sets the environment variables and then starts Eclipse:
+<code bash>
+echo '#!/usr/bin/env sh
+source ~/setup_tqma28
+cd ~/Eclipse
+./Eclipse&' > eclipse_tqma28.sh && chmod u+x eclipse_tqma28.sh
+</code>
+By right click and ''Add to panel...'', and there in the selection window ''Custom Application Launcher'' a "launcher" can be added to a window bar:
+{{:eclipse:eclipse_launcher_with_environment.png?nolink&600}}
+===== Creating a new cross compiler project =====
+  * Menu ''File-->New-->C Project''
+  * Type in the name of the project and select with the ''Cross GCC'' the ''Cross-Compile Project'' as ''Project type''
+  * Select the path to the Cross Compiler via ''Browse'' and type in the prefix of the toolchain in the next window
+<code>
+(e.g.:
+Prefix: arm-none-linux-gnueabi-
+Path: /opt/freescale/usr/local/gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin
+</code>
+  * Press ''Finish'' in the next window.
+===== Creating a project from existing sources =====
+Requirements:
+  * Source code exists
+  * Makefile exists
+  * Project can be built manually at the console
+  - Start Eclipse: ''user@ubuntu:~/Downloads/Eclipse$ ./Eclipse&''
+  - Create a new project: in menu with ''File > New > C Project''
+  - Assign a project name in the wizard (e.g. Hello World) and remove the checkmark at ''use default location''. Then specify the location of the existing project e.g. ''/home/user/src/hello_world/''.
+  - Select ''Cross-Compile Project'' as project type and ''Cross GCC'' as toolchain.
+  - Close the wizard with ''Finish''.
+ - The project with existing source files should now show up on the left of the Project Explorer. Now the automatic makefile has to be disabled in the project properties.
+  - Right click on the project name and select ''Properties'' in the context menu. Select menu item ''C/C++ Build'' in the setting dialog. Turn off the option ''Generate Makefiles automatically'' there.
+{{:eclipse:screenshot-properties_for_hello_world.png?nolink}}
+ Build the project with a click on the hammer.
+  - The binary with the additional information about the architecture, in our case "arm", is in the Project Explorer after a successful build.
+{{:eclipse:screenshot-project_explorer.png?nolink}}
+<WRAP round info>
+The wrong compiler was chosen if the host architecture (e.g. x86) is stated instead of "arm". See also
+[[en:eclipse#configuration]]
+</WRAP>
+===== Cross compiling with Eclipse =====
+In Eclipse a project can be compiled for a different platform. Therefore a call of the target-specific compiler is required. Using the C compiler that comes with the package LTIB, the necessary settings in Eclipse are illustrated here. For this example, this is GCC 4.3.3.
+\\ 1. Note the path to the compiler:
+<code>
+/opt/freescale/usr/local/gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc
+</code>
+\\ 2. Open properties of an Eclipse project (right click on the project in Project Explorer -> Properties) and note the configuration shown above.
+\\ 3. Click on ''Settings'' under ''C/C++ Build'' and mark ''GCC C Ccompiler'' at ''Tool Settings''.
+\\ 4. Change the command ''gcc'' to
+<code>
+/opt/freescale/usr/local/gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc
+</code>
+\\ 5. Now the include directory of the target Linux has to be given to Eclipse to compile. For this purpose expand ''GCC C Compiler'' and select the entry ''includes''.
+\\ 6. Add ''/opt/ltib/src/kernel/linux-2.6-denx/include''.
+\\ 7. Repeat step 4 for the ''GCC Linker''.
+\\ 8. Click on Libraries under the ''GCC Linker''.
+\\ 9. Add the directories ''/opt/ltib/rootfs/lib'' and ''/opt/ltib/rootfs/usr/lib'' to the ''Library search path(-L)''.
+\\ 10. Repeat step 4 for the ''GCC Assembler'', but with the command
+<code>
+/opt/freescale/usr/local/gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-as
+</code>
+\\ 11. Open the tab ''Binary Parsers'', deselect the Elf Parser and select the GNU Elf Parser.
+\\ 12. Change its ''addr2line Command'' to
+<code>
+/opt/freescale/usr/local/gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-addr2line
+</code>
+\\ 13. Change its ''c++filt Command'' to
+<code>
+/opt/freescale/usr/local/gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-c++filt
+</code>
+\\ 14. Apply changes with Apply and OK.
+Now the project for the target hardware is built in the chosen configuration. To copy the created binary to the RootFS the following has to be done:
+In the project properties click on ''Build Steps'' under ''C/C++ Build -> Settings'' and enter the following command at the ''Post-build steps'':
+<code>
+cp /<workspace>/<project>/<Configuration>/<output binary> /opt/ltib/rootfs/home/<user>/
+</code>
+<WRAP round info>
+Copying directly into LTIB RootFS only works if the user rights of Eclipse permit to write to that location. The rights of the target directory must be set accordingly before, if necessary.
+</WRAP>
+===== Demo project =====
+[[:Eclipse:hello_world.zip|]]
+A "Hello World" demo project was created. With a correctly installed and configured ELDK this project should compile with Eclipse and CDT.
+To import the project simply select ''File > Import...'' in the menu. Select ''Existing Projects into Workspace'' in the wizard.
+{{ :Eclipse:screenshot-import.png?200 |}}
+In the next form select the downloaded ZIP archive and complete the import with "Finish".
+{{ :Eclipse:screenshot-import-1.png?200 |}}
+<WRAP round tip>
+Should there be problems when compiling, you can first run the build process on the console with a direct call of ''make''. It will then create an executable program.
+</WRAP>
+===== Debugging =====
+  * [[en:eclipse:debugging|Debugging with Eclipse, RSE and gdb]]
+  * [[en:eclipse:debugging_without_rse|Debugging with Eclipse without RSE, but with gdb]]
+===== Sources =====
+  * http://lists.denx.de/pipermail/eldk/2008-February/000079.html
+  * http://cache.freescale.com/files/dsp/doc/app_note/AN3870.pdf
+  * http://lwn.net/images/conf/rtlws11/papers/proc/p09.pdf
+  * http://comments.gmane.org/gmane.comp.embedded.eldk/1
+  * http://wiki.Eclipse.org/CDT/User/FAQ