usr/ports/java/eclipse-cdt
Brad Keifenheim
Brad_Keifenheim at Dell.com
Wed Jul 10 18:33:42 UTC 2013
Hi Oli,
Thanks for the quick reply. I have tried the eclipse-devel port as you suggested and, unfortunately, still do not have a functional setup.
Here are the configurations I've looked at:
/usr/ports/java/eclipse-cdt
-----------------------------------
As mentioned previously, the configuration is invalid (Eclipse Indigo and CDT for Galileo). I'm unable to create a project from existing C++ source.
/usr/ports/java/eclipse + CDT install via help menu
--------------------------------------------------------------
This is Eclipse Indigo and CDT for Indigo. I am unable to attach to a running process for debug, which is a must-have for my team.
/usr/ports/java/eclipse-devel + CDT install via help menu
----------------------------------------------------------------------
This is Eclipse Juno and CDT for Juno. Once again, I'm unable to attach to a running process for debug.
The terminal I start eclipse from shows the following messages after I attempt to attach the debugger:
java.lang.UnsatisfiedLinkError: no spawner in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1681)
at java.lang.Runtime.loadLibrary0(Runtime.java:840)
at java.lang.System.loadLibrary(System.java:1047)
at org.eclipse.cdt.utils.spawner.ProcessFactory.<init>(ProcessFactory.java:39)
at org.eclipse.cdt.utils.spawner.ProcessFactory.getFactory(ProcessFactory.java:51)
at org.eclipse.cdt.dsf.gdb.launching.LaunchUtils.getGDBVersion(LaunchUtils.java:296)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.getGDBVersion(GdbLaunchDelegate.java:299)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:151)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:106)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:94)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:855)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:704)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1047)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1251)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
When inspecting the eclipse-cdt port I encounter several patch files that modify the CDT plugin. I suspect that similar patches are required for the newer editions of the plugin. I have limited experience with FreeBSD, and am looking for any assistance in getting the CDT plugin up and running with Eclipse.
Cheers,
Brad
-----Original Message-----
From: kron [mailto:kron24 at gmail.com]
Sent: Tuesday, July 09, 2013 10:58 PM
To: Brad Keifenheim
Cc: ports at FreeBSD.org
Subject: Re: usr/ports/java/eclipse-cdt
On 2013/07/10 01:20, Brad Keifenheim wrote:
> Hello,
>
> I have installed the eclipse CDT port and have experienced some
> problems. Upon investigation, I believe a significant concern is with
> a mismatch between the CDT plugin and eclipse versions. The eclipse
> port (a dependency of the eclipse-cdt port) installs the Indigo
> release of eclipse. The eclipse-cdt port installs CDT 6.0.2, however,
> which is designed for eclipse Galileo (2 revisions older than Indigo).
> This configuration isn't valid.
>
> For more information, please refer to:
>
> http://www.eclipse.org/cdt/downloads.php
>
> Is there a planned update to fix this issue? (Or better yet to provide
> eclipse Juno or Kepler and the corresponding CDT plugin?)
>
Greetings to Dell from a Dell notebook :-)
I'd welcome upgrading java/eclipse to Juno or Kepler, too.
I know nothing about plans, just pointing to java/eclipse-devel - it installs Juno. I've been using it for a few weeks without problems.
However I'm on my own when dealing with plugins
- I must manage them from inside Eclipse.
I don't use the CDT plugin so this workaround may not work for you.
BR
Oli
More information about the freebsd-ports
mailing list