Differences

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

Link to this comparison view

Next revision
Previous revision
en:eclipse [2011/11/27 21:56] – created petzen:eclipse [2022/08/04 15:02] (current) – external edit 127.0.0.1
Line 8: Line 8:
   * Eclipse Indigo   * Eclipse Indigo
   * CDT 8.0   * 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   * LTIB 9.1.1
   * ELDK 4.2   * ELDK 4.2
  
-===== Installation =====+===== Installation ==== 
 ==== Download complete package ==== ==== Download complete package ====
-In the repositories Ubuntu 10.04 provides the Eclipse Galileo. The version of CDT for Eclipse Galileo is 6.0.2, this does not yet support features for cross-compiling. For Ubuntu 10.04 we get the packed version of Eclipse Indigo with CDT 8.0. These and possibly newer ones are available at the following download page:+In the repositories Ubuntu 10.04 provides the Eclipse Galileo. The version of CDT for Eclipse Galileo is 6.0.2, this does not yet support features for cross-compiling. For Ubuntu 10.04 we get the packed version of Eclipse Indigo with CDT 8.0. These and possibly newer ones are available at the following download page:  
  
 http://www.Eclipse.org/cdt/downloads.php http://www.Eclipse.org/cdt/downloads.php
Line 23: Line 25:
 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 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)''+**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: 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:
Line 30: Line 32:
 user@ubuntu:~$ sudo apt-get install default-jre user@ubuntu:~$ sudo apt-get install default-jre
 </code> </code>
 +
 ==== Installation using apt-get ==== ==== Installation using apt-get ====
 The Eclipse platform is installed with apt-get: The Eclipse platform is installed with apt-get:
Line 37: Line 40:
 </code> </code>
  
-<note warning+ 
-Ubuntu 10.04 supplies the very old Eclipse Galileo. It is recommended to dirctly download a newer packet. See[[Eclipse#Download_complete_package]] +<WRAP round important
-</note+Ubuntu 10.04 supplies the very old Eclipse Galileo. It is recommended to dirctly download a newer packet. See [[Eclipse#download_complete_package]] 
-<note tip>+</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. 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.
-</note>+</WRAP>
  
 ===== Configuration ===== ===== Configuration =====
Line 48: Line 53:
  
 **Environment**: **Environment**:
-<note important>+<WRAP round important>
 Starting Eclipse by double clicking in the file explorer does not take on the environment variables of the shell. Starting Eclipse by double clicking in the file explorer does not take on the environment variables of the shell.
-</note>+</WRAP>
  
 The first way to use Eclipse with the environment variables is to start Eclipse from the console. The first way to use Eclipse with the environment variables is to start Eclipse from the console.
Line 71: Line 76:
 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: 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& |}}+{{:eclipse:eclipse_launcher_with_environment.png?nolink&600}}
 ===== Creating a new cross compiler project ===== ===== Creating a new cross compiler project =====
   * Menu ''File-->New-->C Project''   * Menu ''File-->New-->C Project''
Line 89: Line 94:
   * Project can be built manually at the console   * Project can be built manually at the console
  
-. 
  
  
Line 98: Line 102:
   - Close the wizard with ''Finish''.   - 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?200 |}} + - 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. 
-  Build the project with a click on the hammer. +  - 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.  
-  - 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?200 |}} + 
-<note+{{:eclipse:screenshot-properties_for_hello_world.png?nolink}} 
-The wrong compiler was chosen if the host architecture (e.g. x86) is stated instead of "arm"+ 
-</note>+ 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 ===== ===== 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. 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.
Line 144: Line 159:
 </code> </code>
  
-<note>+ 
 +<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. 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.
-</note>+</WRAP>
  
  
 ===== Demo project ===== ===== Demo project =====
  
-{{:Eclipse:hello_world.zip|}}+[[: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. A "Hello World" demo project was created. With a correctly installed and configured ELDK this project should compile with Eclipse and CDT.
Line 158: Line 174:
 In the next form select the downloaded ZIP archive and complete the import with "Finish". In the next form select the downloaded ZIP archive and complete the import with "Finish".
 {{ :Eclipse:screenshot-import-1.png?200 |}} {{ :Eclipse:screenshot-import-1.png?200 |}}
-<note tip>+ 
 + 
 + 
 + 
 + 
 +<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. 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.
-</note>+</WRAP>
  
-===== Debugging ===== 
-  * [[Eclipse:debugging|Debugging with Eclipse, RSE and gdb]] 
-  * [[Eclipse:debugging_without_rse|Debugging with Eclipse without RSE, but with gdb]] 
  
 +
 +
 +===== Debugging =====
 +  * [[en:eclipse:debugging|Debugging with Eclipse, RSE and gdb]]
 +  * [[en:eclipse:debugging_without_rse|Debugging with Eclipse without RSE, but with gdb]]
  
 ===== Sources ===== ===== Sources =====
Line 173: Line 196:
   * http://comments.gmane.org/gmane.comp.embedded.eldk/1   * http://comments.gmane.org/gmane.comp.embedded.eldk/1
   * http://wiki.Eclipse.org/CDT/User/FAQ   * http://wiki.Eclipse.org/CDT/User/FAQ
- 
  • Last modified: 2022/08/04 15:04