Work on a remote project with Eclipse via SSH?

Try the Remote System Explorer It's a set of plug-ins to do exactly what you want.

Try the Remote System Explorer. It's a set of plug-ins to do exactly what you want.

2 Cool, didn't know about that. Makes my answer somewhat obsolete :) – Lagerbaer Nov 18 '10 at 16:08 1 RSE is still tricky. The best idea from RSE is for Eclipse to do everything over an SSH connection, but that feature isn't yet working.

The working feature involves some server which you need to setup on the Linux box. – Ioan Nov 18 '10 at 17:56 If all else fails, modify the project locally. Then install cygwin or mingw so you get "rsync".

That allows you to efficiently copy the files over SSH to the remote Linux box. And install Putty to get a remote console. Now you only need to memorize this key-sequence "Ctrl+S Alt-Tab Alt-Tab Up Return Alt-Tab Alt-Tab Up Return" (save in Eclipse, go to the console with "rsync", execute it again, go to putty, run the make command on Linux).

– Aaron Digulla Nov 19 '10 at 8:37 Also the RSE guys like to get bug/enhancement reports. – Aaron Digulla Nov 19 '10 at 8:37 1 @Aaron - I've tried that rsync solution before, from a Makefile - which basically would replace your key sequence with one Ctrl+B. The problem is that with this approach I can neither run nor debug from Eclipse.

The RSE indeed sounds like good tool from the job; @Ioan, can you elaborate on what's not working? The RSE wiki seems to list SSH file systems and remote debugging as a current feature... Or I'll just try it out this Monday. – Kos Nov 19 '10 at 13:25.

The very simplest way would be to run Eclipse CDT on the Linux Box and use either X11-Forwarding or remote desktop software such as VNC. This, of course, is only possible when you Eclipse is present on the Linux box and your network connection to the box is sufficiently fast. The advantage is that, due to everything being local, you won't have synchronization issues, and you don't get any awkward cross-platform issues.

If you have no eclipse on the box, you could thinking of sharing your linux working directory via SMB (or SSHFS) and access it from your windows machine, but that would require quite some setup. Both would be better than having two copies, especially when it's cross-platform.

I'm afraid the linux box doesn't even have X11. :) – Kos Nov 18 '10 at 16:09 1 @Kos, you need the X11-server to run where you physically sit - either with a Linux in a virtual machine, or an X11 server for Windows - and Eclipse to run on the Linux server. Ssh just allows for tunneling the network data - you will find compression + "-c blowfish" to help the experience.

– Thorbjørn Ravn Andersen Nov 19 '10 at 5:27 Just to clarify - are you referring to what's called "headless Eclipse" on the remote machine? (Well, provided it even has Java :)). I was looking for a light client-side solution, but having some setup on the remote machine could be an option too.

– Kos Nov 19 '10 at 13:17 2 @Kos: No. X11 works like this: You have a client and a server. The server is where the monitor is connected.It does all the rendering and displaying.

The client (Eclipse in this case) just sends rendering commands to the server. So you must install X11 on Windows and run Eclipse on your Linux box. All you need to do on Linux is set the DISPLAY variable so Eclipse knows where the server is.

– Aaron Digulla Nov 19 '10 at 14:01.

I had the same problem 2 years ago and I solved it in the following way: 1) I build my projects with makefiles, not managed by eclipse 2) I use a SAMBA connection to edit the files inside Eclipse 3) Building the project: Eclipse calles a "local" make with a makefile which opens a SSH connection to the Linux Host. On the SSH command line you can give parameters which are executed on the Linux host. I use for that parameter a makeit.Sh shell script which call the "real" make on the linux host.

The different targets for building you can give also by parameters from the local makefile --> makeit. Sh --> makefile on linux host.

Nice, but cannot be called "transparent" - doesn't allow debugging at the very least. Also could be based on RSync instead of Samba (which is what I had before I posted my original question). – Kos Nov 28 '10 at 16:48.

I'm in the same spot myself (or was), FWIW I ended up checking out to a samba share on the Linux host and editing that share locally on the Windows machine with notepad++, then I compiled on the Linux box via PuTTY. (We weren't allowed to update the ten y/o versions of the editors on the Linux host and it didn't have Java, so I gave up on X11 forwarding) Now... I run modern Linux in a VM on my Windows host, add all the tools I want (e.g. CDT) to the VM and then I checkout and build in a chroot jail that closely resembles the RTE.It's a clunky solution but I thought I'd throw it in to the mix.

My solution is similar to the SAMBA one except using sshfs. Mount my remote server with sshfs, open my makefile project on the remote machine. Go from there.It seems I can run a GUI frontend to mercurial this way as well.

Building my remote code is as simple as: ssh address remote_make_command I am looking for a decent way to debug though. Possibly via gdbserver?

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.