Difference between revisions of "Hacking:Eclipse"

From GIMP Developer Wiki
Jump to: navigation, search
(Why not to use Eclipse to work on Babl, GEGL and GIMP?)
(Miscellanous: add Eclipse links)
Line 110: Line 110:
= Miscellanous =
= Miscellanous =
See also
* [http://www.eclipse.org/ The Eclipse site]
* [https://wiki.gnome.org/Apps/Eclipse Eclipse in the GNOME wiki]
= Problems and solutions =
= Problems and solutions =
See the [[Hacking:Problems_and_solutions| Problems and Solutions page]].
See the [[Hacking:Problems_and_solutions| Problems and Solutions page]].

Latest revision as of 08:39, 3 August 2014

This page will teach you how to set Eclipse IDE to work on the latest source of GIMP from git.

About Eclipse

Why use Eclipse to work on Babl, GEGL and GIMP?

Some of the features that are interesting for C/C++ developers are:

  • cross-referencing: Ctrl click an identifier and it will take you to its definition,
  • call hierarchy,
  • comprehensive search capabilities,
  • built in Git support,
  • Autotools integration,
  • graphical debugger,
  • explore remote systems from within Eclipse,
  • focus on the current task,
  • Bugzilla integration,
  • static code analysis.

and more. Eclipse runs on every platform that can run Java and has a graphical interface.

It is actively developed and maintained from a living community, see the Eclipse community forums.

Why not to use Eclipse to work on Babl, GEGL and GIMP?

Because it's not Emacs :-P

Eclipse is slow.


The following steps describe the process for Eclipse 4.3 'Kepler' on Linux. It is assumed that your workspace for all projects is /home/user/workspace and GIMP will be installed in /home/user/prefix/gimp.

The continuous example uses Babl, because it is small and easy for a start. Where necessary the tutorial describes the differences for GEGL and GIMP.

Prepare the build environment

clone the Babl Git repository into your workspace:

  1. cd /home/user/workspace
  2. git clone git://git.gnome.org/Babl

To the same for GEGL and GIMP.

Get Eclipse

The easiest way is simply to download Eclipse IDE for C/C++ Developers). If you already have a working Eclipse installation and want to upgrade it, then download the following plug-ins:

  • CDT (for C/C++ development),

and optionally

  • Web Developer Tools (to edit HTML, XML and XSL),
  • EGit (for Git integration),
  • Subversive (for Subversion integration),
  • Mylyn Task List (for Bugzilla integration and task focused working),
  • Remote Systems Explorer (to manage files, search, execute commands and debug on remote systems).

Configure Eclipse to work on Babl, GEGL and GIMP

Create projects

  1. Open the C/C++ perspective.
  2. Create the project: File/New/Makefile Project with Existing Code:
    • Leave the field 'Project Name' empty. It will be filled in the next step.
    • Click 'Browse' behind 'Existing Code Location' and select /home/user/workspace/babl.
    • Languages: C (for GEGL also C++).
    • Toolchain for Indexer settings: GNU Autotools Toolchain
  3. Tell Eclipse that it is an Autotools project, so you can build in Eclipse:
    • Right click on the project
    • From the context menu select New/Convert to a C/C++ Autotools project
    • Candidates for conversion: babl; Convert to C or C++: C
    • For Babl you're done, press 'Finish'. Otherwise hit 'Next' button two times.
    • Referenced C/C++ projects: For GEGL: babl, For GIMP: babl and gegl

Share projects with Git

  1. Open the 'Git Repository Exploring' perspective.
  2. Open the 'Git Repositories' view.
  3. Add an existing local Git repositoriy to this view by clicking the button with this tooltip:
    • Directory: Browse, select /home/user/workspace/babl.
    • Make sure that Babl is checked in the search results list.
  4. Open the C/C++ perspective.
  5. Right click on the Babl project, select 'Team/Share Project...':
    • Repository type: Git
    • select repository: the Babl Git repository

It is important to have created the Git repository before connecting to it from Eclipse. Eclipse refuses trying to create the repository in Babl's workspace folder, so we have to keep this order.

Configure build environment

Integrate Autotools

Configure Eclipse to work with XML files

XML files appear either obviously with the extension .xml, but also a some more file formats are based on XML. With Eclipse's XML plug-in you can edit the raw source code, but also work the XML tree structure of an XML file. The following files are known to be XML files:

  • *.bundle Configuration files for gtk-mac-bundler
  • *.modules Configuration files for JHBuild
  • *.svg Vector graphics files
  • *.plist OS X application metadata
  • *.xml DocBook documents, D-Bus service configuration, menu descriptors, the authors list etc.

To be able to edit XML files as such:

  1. Open 'Help/Install new software...'. Install the plug-in XML Editors and Tools. If you want to edit XSL files, also install the XSL Developer Tools.
  2. Open 'Window/Preferences'. Select 'General/Content Types'. Select 'Text' and then 'XML'. Press the 'Add' button and add then enter *.bundle. Repeat the last step also for *.modules, *.plist etc.

Working with Eclipse





See also

Problems and solutions

See the Problems and Solutions page.