can't delete linker library property
 

I found a small problem. I open properties/c/c++build/tool settings/mplink linker/linker information and delete the one entry in "libraries included in linking". This is because I would prefer to define all the libraries in the lkr file. Then I can "clean" and all is well. But if I close eclipse and reopen it, the entry is back. I can't delete it permanently.

Re: Eclipse Plugin Maintaineer?
 

This would be the wrong thing to do. The zip is of the projects, not jars. It is for development.

The only plugin that is actually usable is org.eclipse.cdt.mcc18.toolchain. You can tell Eclipse to Export it as a Deployable Plug-in.

The rest of it is currently incomplete or having strange compilation issues.

Re: Eclipse Plugin Maintaineer?
 

I'm confused. The zip contains no jar file. You earlier instructions said to use that zip instead of the jar that comes with the white paper.

What I did worked, halleujah. But please let me know what I should have done instead.

Thanks - Bill

Re: Eclipse Plugin Maintaineer?
 

I took prograid's plugin and modified it. It just so happens that it's XML-only, so I'm not surprised it worked. (Everything appeared in the right place as far as Eclipse goes.)

As to how to correctly setup and compile this in the future:

Setting up the project:

1. Go to File > Import
2. Select "Existing Projects into Workspace", hit "Next >"
3. Click "Select archive file:"
4. Click "Browse...", and select the downloaded archive file
5. Hit the checkboxes on all 5 projects
6. Hit "Finish"

The projects, by default, will automatically compile.

To package them into jars:

1. Make sure you're in the "Plug-in Development" perspective
2. Right-click on the project you want to package, select "Export"
3. Select "Deployable plug-ins and fragments", hit "Next >"
4. Check the projects you want to export.
5. Select export destination of choice.
6. Make sure that "Package plug-ins as individual JAR archives" is checked. (Using "Include source code" is entirely your digression"
7. Hit "Finish"

Allow to run for a few minutes. You will then have the approrpriate installable JAR. Make note of changes you made to the default configuration; I changed the internal name of some (most?) of the settings.

Note: All the directions above are based on Eclipse 3.1.2.

Re: Eclipse Plugin Maintaineer?
 

Has anyone used this under Linux? I have been using a makefile to compile the code for the robot, but I don't think that the makefile that I am using is 100% correct. I am trying to find an alternative way to compile code for the robot under Linux.

Re: Eclipse Plugin Maintaineer?
 

OK, got it, thanks for clarifying. I've imported the plugin projects into Eclipse, now I can try to use it (i.e. break it...).

If I want to modify the plugin and deploy it, do I have to do anything besides replace the jar file for it to be effective? I know there have been past instructions that indicate what within eclipse has to be deleted to ensure eclipse forgets the old plugin and uses the new one.

Re: Eclipse Plugin Maintaineer?
 

Just to be really clear, you can't test a plugin project in the main eclipse app. You have to tell eclipse to Run/Debug as an Eclipse Application, IIRC.

Do this on a case-by-case basis. I don't have enough experience to tell you. (Although if you increment the version, I suspect you'll have issues.)