Changes between Version 22 and Version 23 of Developer/Eclipse/Information


Ignore:
Timestamp:
Nov 22, 2014, 5:22:16 AM (5 years ago)
Author:
Chris Johns
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Eclipse/Information

    v22 v23  
    11= RTEMS Eclipse Information =
    22
    3 
     3RTEMS provides an Eclipse Plugin you can use to help integrate your work flow with RTEMS.
    44
    55[[TOC(Developer/Eclipse/Information, depth=2)]]
     
    99
    1010There is a plug-in available for RTEMS development with Eclipse.  It is based on CDT.  See also the [wiki:Developer/Eclipse/Plugin user guide].
     11
    1112= Introduction =
    1213
     
    2829
    2930This is a very open ended project which has a number of steps based
    30 upon subprojects or plugins which need to be made available to RTEMS
     31upon sub-projects or plugins which need to be made available to RTEMS
    3132developers.
    3233
     
    4344hardware or anything that costs to verify that their implementation
    4445works with multiple hardware configurations.
     46
    4547= GNU Debugger Integration =
    4648
     
    5052[http://www.eclipse.org/cdt/ CDT (C/C++ Development)] also supports the GDB and provides a fully functional C and C++ Integrated Development Environment (IDE) for the Eclipse platform. Our focus is development on Linux for deployment on Linux, but we are interested in participation from others who would like to extend our work in other directions (e.g. a Windows client, targeting Unix(R) or embedded platforms, wizards for developing applications that use particular library or database or messaging APIs, or extension to other languages). We are looking for contributions from the open source community in the areas of testers,
    5153developers and general users who can help us ensure that the C/C++ tools work well on all the Eclipse platforms and compiler environments.
     54
    5255= Interaction with the Target System =
    5356
     
    6063
    6164There are many sub-projects in there, but some of the interesting ones are: [http://www.eclipse.org/sequoyah/index.php Sequoyah], [http://www.eclipse.org/dsdp/tm Target management(RSE)] and [http://www.eclipse.org/rtsc RTSC]
     65
    6266= RSE =
    6367
     
    6670
    6771One of the interesting aspects of this is how Wind River has adopted Eclipse as the platform for vxWorks and Embedded Linux development. It appears that they are putting significant effort into contributing code back to the DSDP platform and trying to help create open standards for this type of development environment. It would be nice if this work ends up meaning that an Eclipse platform could talk to a target server on either vxWorks, Linux or RTEMS.
     72
    6873= RTSC =
    6974
     
    7277
    7378[http://eclipse.org/ercp/ Embedded Rich Client Platform (eRCP)]. The intent of this project is to extend the Eclipse Rich Client Platform (RCP) to embedded devices. eRCP is largely a set of components which are subsets of RCP components. It basically enables the same application model used on desktop machines to be used on devices.
     79
    7480= MTJ =
    7581
    7682[http://www.eclipse.org/dsdp/mtj/ Mobile Tools for Java (MTJ)] The scope of the Mobile Tools for the Java Platform (MTJ) project is to extend the Eclipse platform to enable developers to develop, debug, and deploy mobile Java applications to emulators and real devices. The project will develop frameworks that can be extended by tool vendors and tools that can be used by third-party developers.
     83
    7784= Sequoyah =
    7885
    7986[http://www.eclipse.org/sequoyah/index.php Sequoyah] project's purpose is to be focused on the needs of all mobile developers. Inheriting components from TmL, MTJ and Pulsar projects, Sequoyah intends to remove the artificial barriers of Linux and Java in order to provide a home for all Eclipse mobile developers.
    80 = FindBugs Eclipse Plugin =
    81 
    82 [http://marketplace.eclipse.org/content/findbugs-eclipse-plugin FindBugs] is a defect detection tool for Java that uses static analysis to look for more than 200 bug patterns, such as null pointer dereferences, infinite recursive loops, bad uses of the Java libraries and deadlocks. FindBugs can identify hundreds of serious defects in large applications (typically about 1 defect per 1000-2000 lines of non-commenting source statements). FindBugs is open source, has been downloaded more than 230,000 times and is used by many major companies and financial institutions.
     87
     88= !FindBugs Eclipse Plugin =
     89
     90[http://marketplace.eclipse.org/content/findbugs-eclipse-plugin FindBugs] is a defect detection tool for Java that uses static analysis to look for more than 200 bug patterns, such as null pointer dereferences, infinite recursive loops, bad uses of the Java libraries and deadlocks. !FindBugs can identify hundreds of serious defects in large applications (typically about 1 defect per 1000-2000 lines of non-commenting source statements). !FindBugs is open source, has been downloaded more than 230,000 times and is used by many major companies and financial institutions.
    8391
    8492Using this plugin one can make his life easier doing [http://java.sun.com/javase/technologies/realtime/index.jsp Real-time Java Programming] by detecting known bug patterns in software.
     
    8694The [http://gcc.gnu.org/java/ GNU Java Compiler], currently doesn't work with RTEMS, see [http://www.rtems.com/wiki/index.php/GNUJavaCompiler 1] but [http://www.aero-project.org/ AERO­VM ­ Hard Real­Time Java Virtual Machine] seems to work on boards with Leon processors.
    8795
    88 (this plugin may be of use in the future when the GCC­Java will work with RTEMS)
     96(this plugin may be of use in the future when the GCC­ Java will work with RTEMS)
    8997
    9098See also: http://rtjava.blogspot.com/search/label/RTSJ
    91 = NDS Managedbuilder =
    92 
    93 Provided that RTEMS can run on arm/nds (Nintendo DS) one can make use of [http://marketplace.eclipse.org/content/nds-managedbuilder NDS Managedbuilder], an Eclipse CDT plugin for C/C++ development for the Nintendo DS target system. It supports DevkitPro compiler/debugger.
     99
     100= NDS Managed Builder =
     101
     102Provided that RTEMS can run on arm/nds (Nintendo DS) one can make use of [http://marketplace.eclipse.org/content/nds-managedbuilder NDS Managedbuilder], an Eclipse CDT plugin for C/C++ development for the Nintendo DS target system. It supports !DevkitPro compiler/debugger.
    94103
    95104 *  easy to use managed build system based on the GNU toolchain
     
    97106 *  different project types
    98107 *  NDS ROM - ARM9 Sources + NDS Tool
    99  *  NDS ARM7 Code - ARM7 Sources + ObjCopy
     108 *  NDS ARM7 Code - ARM7 Sources + !ObjCopy
    100109 *  NDS ARM7 Library - generates a static link lib
    101110 *  NDS ARM9 Library - generates a static link lib
    102  *  includes ObjCopy and NDS-Tool in the toolchain
     111 *  includes !ObjCopy and NDS-Tool in the toolchain
    103112 *  integrate the ARM gdb debug server
    104 = CVS Version Tree =
    105 
    106 [http://marketplace.eclipse.org/content/cvs-version-tree Eclipse Version Tree Plugin] is an easy to use, graphical version tree for project artifacts hosted in a CVS repository. It is a graphical replacment for Eclipse resource history. Supports different layout styles, customization and convenience features
    107 = CVS-Git integration =
     113
    108114= EGit plugin =
    109115
     
    121127
    122128Some people even use [http://stackoverflow.com/questions/321196/is-git-with-cvs-faster-than-cvs-alone Git as a CVS client]
     129
    123130= LEON C/C++ IDE for Eclipse =
    124131
     
    128135- LEON IDE extends the CDT environment to include support for development and debugging using the tools provided by Aeroflex Gaisler.
    129136Supported toolchains:
    130 ? RTEMS 4.6.5 1.0.19
    131 ? RTEMS 4.7.99.2 1.0.4
     1371. RTEMS 4.6.5 1.0.19
     1381. RTEMS 4.7.99.2 1.0.4
    132139
    133140Also see [http://www.gaisler.com/cms/index.php?option=com_content&task=view&id=150&Itemid=31 LEON/ERC32 RTEMS Cross Compilation System (RCC)] a cross-compilation system for both ERC32 and LEON processors.
     141
    134142= Embedded Linux Development Kit =
    135143
     
    141149
    142150Like a Wizard/Editor for Eclipse to configure RTEMS for a certain Application e.g. max number of tasks, semaphores (http://www.rtems.com/wiki/index.php/ApplicationConfigurationGUI) or another project is to support RTEMS as a run-time in Argo UML (http://www.rtems.com/wiki/index.php/ArgoUML)
     151
    143152= RTEMS Eclipse Plug-in Project =
    144153
    145154= Repository =
    146155
    147 
    148 The [http://www.rtems.com/cgi-bin/cvsweb.cgi/rtems-eclipse-plug-in/#dirlist project repository] is hosted by OAR and is available via <tt>:pserver:anoncvs@www.rtems.org:/usr1/CVS</tt> and module <tt>rtems-eclipse-plug-in</tt>.  It contains the following submodules:
    149  *  <tt>org.rtems.cdt</tt>: Plug-in for further development
    150  *  <tt>org.rtems.feature</tt>: Deployable components
    151  *  <tt>org.rtems.update</tt>: Update site
    152  *  <tt>org.rtems.cdt.toolchain</tt>: Initial plug-in
    153  *  <tt>org.rtems.cdt.toolchain2</tt>: Temporary development plug-in (obsolete)
     156The git://git.rtems.org/rtems-eclipse-plug-in.git project repository  module contains the following submodules:
     157 *  '''org.rtems.cdt''': Plug-in for further development
     158 *  '''org.rtems.feature''': Deployable components
     159 *  '''org.rtems.update''': Update site
     160 *  '''org.rtems.cdt.toolchain''': Initial plug-in
     161 *  '''org.rtems.cdt.toolchain2''': Temporary development plug-in (obsolete)
     162
    154163= Current Status =
    155164
    156 
    157165The plug-in is usable and tested on Cygwin, MinGW, MacOS X and UNIX.  See also the [wiki:Developer/Eclipse/Plugin user guide].
     166
    158167= Features =
    159168
     
    162171 *  No dependency on special environment variable settings (including PATH)
    163172 *  Automatic detection of tool options via the standard Makefile interface
     173
    164174= TODO List =
    165175
     
    173183 *  More stable scanner configuration (this is more a [http://wiki.eclipse.org/CDT/ScannerDiscovery61 CDT internal issue]), scanner is currently not working for Cygwin
    174184 *  Per configuration platform and BSP paths (this simplifies migration)
     185
    175186= Initial Implementation =
    176187
     
    201212The detail document for the initial implementation including its
    202213limitations can be found [wiki:Initial_RTEMS_Eclipse_Plug-in here].
     214
    203215= Revision History =
    204216
    205217
    206218 *  2008-12-09: Daron Chabot provided [http://www.rtems.com/cgi-bin/cvsweb.cgi/rtems-eclipse-plug-in/org.rtems.cdt.feature deployable components] of the plug-in and an [http://www.rtems.com/cgi-bin/cvsweb.cgi/rtems-eclipse-plug-in/org.rtems.cdt.update update site].
    207 
    208219 *  2008-12-04: Sebastian Huber finished the development of the alternative implementation and provided a [http://www.rtems.com/cgi-bin/cvsweb.cgi/rtems-eclipse-plug-in/org.rtems.cdt common basis] for further development.
    209 
    210220 *  2008-11-23: Daron Chabot made it work on Mac and Linux.
    211 
    212221 *  2008-11-21: Sebastian Huber started an [http://www.rtems.com/cgi-bin/cvsweb.cgi/rtems-eclipse-plug-in/org.rtems.cdt.toolchain2 alternative implementation].
    213 
    214222 *  2008-11-20: OAR provided a [http://www.rtems.com/cgi-bin/cvsweb.cgi/rtems-eclipse-plug-in/#dirlist repository] for development
    215 
    216223 *  2008-11-20: Robert Fu published the [wiki:Initial_RTEMS_Eclipse_Plug-in initial implementation], which was only tested on Windows.