Developer FAQ
How to contribute?
See the How to contribute page.
Developer FAQ
How can I get the sources of the Rodin platform?
There are two options for getting the sources of the Rodin platform:
- The safe option is to download the source bundle which is made available with each platform release. This ensures that you will get a consistent set of source files, albeit maybe a bit outdated.
- The other option is to fetch the sources from Subversion, which allows to get their latest version. The Rodin developers strive for keeping theses sources usable (i.e. they should always compile and pass unit tests), but breakage can happen.
Installing the source bundle in Eclipse
To install the bundled sources, you first have to download the bundle from SourceForge. It takes the form of a ZIP file named rodin-VERSION-sources.zip. Then, in Eclipse, click
In the Import popup, select and click . Then tick and enter the path to the source bundle you have just downloaded. Ensure that all projects are ticked and click . Your workspace gets populated with the source projects of the Rodin platform and Eclipse starts building.Installing the sources from Subversion in Eclipse
To install the sources from Subversion, in Eclipse click https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp and click . In the tree displaying the subversion repository, select path trunk/RodinCore/org.rodinp.releng and click . Your workspace now contains the project org.rodinp.releng.
, then select in the Import popup and click twice. In the Url textbox, enterTo install the other source projects, click again
, but this time select and click . When asked for a File name, enter the path to file org.rodinp.releng/rodin-core.psf in your workspace and click . Eclipse then fetches the other source projects of the Rodin platform into your workspace (this can take some time).Using Rodin as Target Platform
From Rodin 1.3 on, source bundles can be included in a target platform configuration.
Using Rodin-SVN from Eclipse consumes too much memory
Running the Rodin platform from Eclipse can consume a lot of RAM and become impractical on a small machine. If you fall in this case, you can generate a product and use it as if it was a normal release.
How do I generate a Rodin product from sources?
In the project org.rodinp.platform, right-click on Rodin.platform and select
. Choose and click on type Rodin for the Root directory, and choose the Destination directory. Then click on .How to build Rodin headless?
When releasing a new version of the Rodin platform, the Rodin team builds the platform headless (i.e. using batch scripts rather than Eclipse GUI). The process used for that is described in Building Rodin Headless. Alternatively, the Rodin team has also set up a CruiseControl server for checking that builds do not break.
How to generate Rodin source plugins for a Target Platform configuration ?
For source plugins to work properly in a target platform configuration, use the Ant script explained in this page.
How do I collect debug information from the Rodin platform?
You may see the log in the console by appending -consoleLog to the rodin executable: rodin -consoleLog
You may add specific debug informations by setting specific options: rodin --debug options.file -consoleLog
where
contains something like:
org.pluginname/debug = true org.pluginname/debug/optionaldebug = true
where optionaldebug may be found in the
file in the rodin source repository.
How do I submit a patch?
Good practises for patch submission are described here.
How do I track memory leaks?
If you suspect that some memory isn't freed, you may find some useful directions on how to track memory leaks here.
How do I report a bug.
See the How to contribute page.
How do I save the models ?
After the separation between a file (IRodinFile) and its root (a IInternalElement), that occurred in version 0.9.2, model saving is no more achievable through internal elements. Instead, you have to save the IRodinFile.
IInternalElement element = ... element.getRodinFile().save(...);
How do I add a new attribute to existing elements (e.g. Event-B event)?
You need to extend the following extension point org.rodinp.core.attributeTypes
to declare the new attribute.
Note: There is no constraint on which element type this attribute type associated with. In principle, any attribute type can be attached to the any internal element type.
The detail steps are described in the following page Extending the Rodin Database.
How do I extend the Event-B structure editor (the Edit Tab of the Event-B editor) for editing an attribute (which I added to the Rodin DB as described here)?
You need to extend the following extension point org.eventb.ui.editorItems
to declare the two different elements:
- How the attribute is going to be displayed/edited. This is done by declaring one of the following elements:
textAttribute
,choiceAttribute
ortoggleAttribute
.
- The relationship between the attribute and internal elements. This is done by declaring an
attributeRelation
element. Note: In fact, this relationship declares which element allows to have this attribute, which is not something enforce when the attribute is added as described here.
The detail steps are described in the following page Extending the Structure Editor.