|
| Re: Custom plugin will not install [message #331784 is a reply to message #331783] |
Mon, 22 September 2008 14:16   |
Eclipse User |
|
|
|
Originally posted by: zx.code9.com
Jim Adams wrote:
> I have created a plugin that provides a toolchain definition for a
> compiler & linker to be run in the Eclipse CDT. I can debug the
> toolchain plugin without any problems but when I export it and drop the
> jar file into the plugin directory of an eclipse CDT install, eclipse
> does not load it. I followed the directions outlined in the "Plug-in
> development 101, Part 1" article by Chris Aniszczyk, i.e organized the
> manifests, Externalized the strings, specified the build configuration
> and then ran the Export Wizard, but to no avail. Is there something
> else I am missing?
If you're using Eclipse 3.4, you should be using the "dropins" directory.
http://wiki.eclipse.org/Equinox_p2_Migration_Guide
Cheers,
~ Chris
|
|
|
|
| Re: Custom plugin will not install [message #331795 is a reply to message #331793] |
Mon, 22 September 2008 18:09 |
| Eclipse User |
|
|
|
Originally posted by: zx.code9.com
Jim Adams wrote:
> Thanks Chris for the prompt response. I tried using the dropins folder
> using the structure outlined in the link you suggested but still had no
> success with having Eclipse seeing or loading the plugin.
>
> That "Equinox p2 Migration Guide" page mentioned .link files and
> Extension folders. When I export my plugin I do not have those two
> items. Is that the problem?
>
> This is my first attempt at writing a plugin so I get the feeling I am
> overlooking something very simple. Again any help and direction would
> be greatly appreciated!
When you drop your plug-in in the dropins directory and are ready to
launch Eclipse, do this.
../eclipse -console
This should have a console come up with an osgi> prompt
Typing "ss" should show you the state of the whole environment.
In our case, what we want to do is type:
"start <your bundle id>"
If there is trouble starting your bundle, you should see why.
You can also type
"diag <your bundle id>"
To see if it gives you why your bundle isn't working.
Let's try that. Post any traces you get from running those commands to
see if we can get the bottom of this. My guess is that we may be missing
some dependencies here ;)
Cheers,
~ Chris
~ Chris
|
|
|
|
| Re: Custom plugin will not install [message #331800 is a reply to message #331799] |
Mon, 22 September 2008 22:04 |
| Eclipse User |
|
|
|
Originally posted by: zx.code9.com
Jim Adams wrote:
> Hi Chris,
>
> Thanks for your response.
>
> I did as you suggested and started eclipse with ./eclipse -console.
> When I ran ss my package (bundle) did not show up. This is where I
> think that I am missing something trivial. It does not appear to even
> recognize my jar file as a plugin.
>
> Thanks again for your assistance!
When you are exporting your plug-in, where are you putting it?
There should be a "dropins" directory if you're using Eclipse 3.4 to put
new plug-ins into. When Eclipse is started, p2 (the provisioning system)
will detect a plug-in is there and install it into the running system.
But let me get a little more info about your setup. I assume you have
this setup:
1) development environment with CDT and who knows what else
2) target environment which just has CDT?
I assume you build and develop the plug-in using the first eclipse
installation and than export the plug-in into the target Eclipse
installation?
Is that how things are working?
Cheers,
~ Chris
|
|
|
|
Powered by
FUDForum. Page generated in 0.04461 seconds
] 
Search
Help
Register
Login
Home
