Re: [Avr-eclipse-devel] Any hints on how to build the plugin myself

[Kees B. <ke...@ij...>]

Thanks Thomas,

This is exactly what I needed. Great. It might be useful
for other people too.

BTW. The change I'm going to try is fairly simple. The list of
paths to find avr/io.h (for example) contains /usr/. That's
causing Eclipse to be non-responsive for more than a minute.
And on one system it is even much longer. (( Lots of NFS
mounts on /usr/src, with lots of MBs to search. )) Also deep
search /home/ isn't good for me. There is way too much data
inthere. For me, I'll be happy with just /usr/local/, /usr/lib/

-- Kees

On 21-09-12 17:18, Thomas Holland wrote:
> Hello Kees,
>
> 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 
> <http://maven.apache.org/download.html>. 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
>
>
>
>
>
>
> On 21.09.2012 13:48, Kees Bakker wrote:
>> Hi,
>>
>> I was looking for some hints on how to rebuild / debug the
>> plugin myself. I've "imported" the projects in Eclipse, but
>> I don't see which one is the main project.
>>
>> What are the steps to follow?
>>
>> Kind regards,
>> Kees Bakker
>>
>
>
> ------------------------------------------------------------------------------
> Got visibility?
> Most devs has no idea what their production app looks like.
> Find out how fast your code is with AppDynamics Lite.
> http://ad.doubleclick.net/clk;262219671;13503038;y?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>
>
> _______________________________________________
> Avr-eclipse-devel mailing list
> Avr...@li...
> https://lists.sourceforge.net/lists/listinfo/avr-eclipse-devel