Date: Thu, 11 Jul 2013 09:51:16 +0200 From: kron <kron24@gmail.com> To: Brad Keifenheim <Brad_Keifenheim@Dell.com> Cc: "ports@FreeBSD.org" <ports@FreeBSD.org> Subject: Re: usr/ports/java/eclipse-cdt Message-ID: <51DE63F4.40900@gmail.com> In-Reply-To: <975552A94CBC0F4DA60ED7B36C949CBA08D42D2616@shandy.Beer.Town> References: <975552A94CBC0F4DA60ED7B36C949CBA08D42D1C8E@shandy.Beer.Town> <51DCDBBE.60108@gmail.com> <975552A94CBC0F4DA60ED7B36C949CBA08D42D2616@shandy.Beer.Town>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013/07/10 20:33, Brad Keifenheim wrote: > 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. Sorry, my approach seems to be too limited for CDT. You may get some advice on freebsd-eclipse@ or freebsd-java@ but the eclipse port is without a maintainer so chances are somewhat doubtful. I feel your pain. I was in a similar situation some time ago, waiting for a must-have upgrade of eclipse. In the meantime I just used a VirtualBox virtual machine with Linux for eclipsing. Moved the whole project to the VM a run "ssh -X virtlnx eclipse" instead of plain "eclipse". Performance was OK, the only drawback was managing project files from CLI: they weren't local, one had to remember to ssh to the VM. A side note: I've been a FreeBSD and Linux user for about 15 years and I prefer FreeBSD for most tasks. However, if my work was 99% about eclipsing I would use Linux for my workstation. Eclipse's development seems to ignore BSDs and FreeBSD's ports are often too delayed. To be fair to our porters, it isn't an easy work and I just admire their bravery. Some time ago I tried to update the eclipse port myself and failed. Monumentally :-) I'm happy that my eclipsing is just a minor part of my work and I don't need special plugins like CDT. BR, Oli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51DE63F4.40900>