Date: Wed, 10 Jul 2013 13:33:37 -0500 From: Brad Keifenheim <Brad_Keifenheim@Dell.com> To: kron <kron24@gmail.com> Cc: "ports@FreeBSD.org" <ports@FreeBSD.org> Subject: RE: usr/ports/java/eclipse-cdt Message-ID: <975552A94CBC0F4DA60ED7B36C949CBA08D42D2616@shandy.Beer.Town> In-Reply-To: <51DCDBBE.60108@gmail.com> References: <975552A94CBC0F4DA60ED7B36C949CBA08D42D1C8E@shandy.Beer.Town> <51DCDBBE.60108@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Oli,
Thanks for the quick reply. I have tried the eclipse-devel port as you sugg=
ested 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 C=
DT 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 runni=
ng 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 atte=
mpt 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>(ProcessFacto=
ry.java:39)
at org.eclipse.cdt.utils.spawner.ProcessFactory.getFactory(ProcessF=
actory.java:51)
at org.eclipse.cdt.dsf.gdb.launching.LaunchUtils.getGDBVersion(Laun=
chUtils.java:296)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.getGDBVersio=
n(GdbLaunchDelegate.java:299)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugS=
ession(GdbLaunchDelegate.java:151)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugg=
er(GdbLaunchDelegate.java:106)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLa=
unchDelegate.java:94)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(Launc=
hConfiguration.java:855)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(Launc=
hConfiguration.java:704)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(Debug=
UIPlugin.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 m=
odify the CDT plugin. I suspect that similar patches are required for the n=
ewer 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 E=
clipse.
Cheers,
Brad
-----Original Message-----
From: kron [mailto:kron24@gmail.com]=20
Sent: Tuesday, July 09, 2013 10:58 PM
To: Brad Keifenheim
Cc: ports@FreeBSD.org
Subject: Re: usr/ports/java/eclipse-cdt
On 2013/07/10 01:20, Brad Keifenheim wrote:
> Hello,
>=20
> I have installed the eclipse CDT port and have experienced some=20
> problems. Upon investigation, I believe a significant concern is with=20
> a mismatch between the CDT plugin and eclipse versions. The eclipse=20
> port (a dependency of the eclipse-cdt port) installs the Indigo=20
> release of eclipse. The eclipse-cdt port installs CDT 6.0.2, however,=20
> which is designed for eclipse Galileo (2 revisions older than Indigo).=20
> This configuration isn't valid.
>=20
> For more information, please refer to:
>=20
> http://www.eclipse.org/cdt/downloads.php
>=20
> Is there a planned update to fix this issue? (Or better yet to provide=20
> eclipse Juno or Kepler and the corresponding CDT plugin?)
>=20
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 instal=
ls 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?975552A94CBC0F4DA60ED7B36C949CBA08D42D2616>