Skip to content
A fork of avr-eclipse
Java Other
  1. Java 98.9%
  2. Other 1.1%
Branch: R2.4_Maintenan…
Clone or download
Pull request Compare This branch is 1 commit ahead, 69 commits behind mnlipp:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
de.innot.avreclipse-updatesite
de.innot.avreclipse.core.managedbuildsystem
de.innot.avreclipse.core.test
de.innot.avreclipse.core
de.innot.avreclipse.debug.core
de.innot.avreclipse.debug.gdbservers
de.innot.avreclipse.debug.tests
de.innot.avreclipse.debug.ui
de.innot.avreclipse.doc
de.innot.avreclipse.feature
de.innot.avreclipse.master
de.innot.avreclipse.p2repository
de.innot.avreclipse.source
de.innot.avreclipse.templates
de.innot.avreclipse.tests.swtbot
de.innot.avreclipse.ui.tests
de.innot.avreclipse.ui
de.innot.avreclipse.utils
de.innot.avreclipse
.gitignore
README.md

README.md

avr-eclipse-plugin

The AVR Plugin has no "master" project. It is a collection of projects, some of them containing just source code, some of them only relevant for building the plugin. The XML files within these projects determine their function and are responsible for the integration of the different parts into Eclipse.

But debugging the plugin is easy: just right click on any project, e.g. de.innot.avreclipse.core, and select "Debug as > Eclipse Application". A new instance of Eclipse is started which will include all of the projects in the AVR Plugin. You can set breakpoints and debug to your hearts content. Please be aware, that the original Eclipse instance, the one containing the source code of the plugin, should not have the AVR Plugin installed as this may lead to conflicts between an installed plugin and the plugin under test (this problem can of course be configured away, but it is tedious)

Building the plugin for redistribution is a different procedure, actually separate from Eclipse itself. I have taken this approach because it is more robust and predictable than the built-in Eclipse tools.

To build the plugin you need Maven. Once you have Maven installed you can open a Command Shell and change to the "de.innot.avreclipse-releng" directory. Then you just need to run "mvn clean install" and the plugin will be build, including running all tests. The first run will probably take just about forever, because maven will download a large number of required tools and libraries, including the core parts of Eclipse itself. But this stuff is cached, so further builds should be quicker (they are still slow, but hey, building is not something needed every few minutes).

If the build is successful the finished plugin will be located in the "de.innot.avreclipse-p2repository" project. A refresh of this project may be necessary to make the new files visible in Eclipse.

Please be aware that the "master" branch of the Git repo may not build. I haven't done builds for quite some time so things are in a bit of disarray. However the "R2.4.0" branch should build successfully and is probably the best starting point for working on the plugin.

Cheers,

Thomas

You can’t perform that action at this time.