Using Rodin as Target Platform: Difference between revisions

From Event-B
Jump to navigationJump to search
imported>Nicolas
imported>Nicolas
mNo edit summary
Line 1: Line 1:
When developing plug-ins for Rodin, it is somewhat cumbersome to have to all sources from the SVN repository, or to import them in the workspace somehow, just to be able to read them.
When developing plug-ins for Rodin, it is somewhat cumbersome to have to download all sources from the SVN repository, or to import them in the workspace somehow, just to be able to read them.
Using a target platform is a convenient alternative.
Using a target platform is a convenient alternative.



Revision as of 14:50, 4 May 2010

When developing plug-ins for Rodin, it is somewhat cumbersome to have to download all sources from the SVN repository, or to import them in the workspace somehow, just to be able to read them. Using a target platform is a convenient alternative.

Configuring a Target Platform

Window > Preferences > Plug-in Development > Target Platform: click "Add..."

Select "Nothing: Start with an empty target definition".

On the next page, in "Locations" tab, we will add places where Rodin bundles can be found.

Adding a source directory

It is important to add the source directory first, so that javadoc attachment works.

Click "Add...", select "Directory" then browse to the directory containing Rodin sources generated for inclusion in a Target Platform and click "Finish".

This makes Rodin sources available. For instance, pressing F3 on a reference of the IAxiom interface in client code opens an editor that shows the source code in IAxiom.java.

Adding a Rodin installation

Click "Add...", select "Installation" then browse to the target Rodin installation directory and click "Finish".

This allows to build a Rodin plug-in, but by itself it is not sufficient to read the sources as a Rodin installation only contains .class files.