Tools and requirements

Prerequisites

Tools

  • Download and install Eclipse 4.2, which will serve as a target for development.
  • You can use Eclipse 4.2 for development too, but the newer Java tools are much better. I always the latest Eclipse for developing.
  • The debugger support code has different projects for R15, R16, 17 and 18, due to changes to the compiler and/or runtime. You need all these versions installed if you make changes to the debugger.
  • In your development Eclipse, install a Java 1.6 JDK and the EGit, Erlide and Xtend plugins.
  • Other recommended plugins: AnyEdit.
  • A note about using more recent versions of Java/Eclipse/Erlang: they should work, but if the target is not 1.6/4.2/R16B, then you might use things that are not available in the base configuration or have changed since and then there will be errors (at compile-time or run-time).

Setup

  • Start Eclipse and
    • configure the Plugin development environment by setting the target environment to the 4.2 installation
    • configure Erlide with runtimes: one of all supported versions (because we need the debugger to get compiled with each of them).
    • restart
  • In your Eclipse workspace, import all projects from the erlide repository, even the optional ones (wrangler, cover, tracing). This will let you know if you happen to change something that affects them.
  • Close the wrangler.refactoring.codeinspection plugin, it only compiles on the build server. (Alternatively, leave it open and live with a couple of compilation errors).
  • Configure some settings by importing the preferences from meta/config, this will help to keep a consistent view of the code.

  • The projects should build without errors.

  • The “Run” button’s (green with white arrow) popdown menu should contain a few entries: some junit_* ones that run the unit tests for the respective project and “Erlide_tests” that launches a new Eclipse instance that uses the local erlide code (including any changes you made). You can import in there all projects from org.erlide.ui.tests/projects

Did you find errors in the documentation? Do you have improvements to suggest? Suggest edits!