Work on a remote project with Eclipse via SSH

Question

I have the following boxes    A Windows box with Eclipse CDT    A Linux box  accessible for me only via SSH    Both the compiler and the hardware required to build and run my project is only on machine B   I d like to work  transparently  from a Windows box on that project using Eclipse CDT and be able to build  run and debug the project remotely from within the IDE   How do I set up that    The building will work  Any simpler solutions than writing a local makefile which would rsync the project and then call a remote makefile to initiate the actual build  Does Eclipse managed build have a feature for that  The debugging will work  Preferably - the Eclipse CDT code indexing will work  Do I have to copy all required header files from machine B to machine A and add them to include path manually

User · Answer

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?

User · Answer

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

User · Answer

I tried ssh -X but it was unbearably slow   I also tried RSE  but it didn t even support building the project with a Makefile  I m being told that this has changed since I posted my answer  but I haven t tried that out   I read that NX is faster than X11 forwarding  but I couldn t get it to work   Finally  I found out that my server supports X2Go  the link has install instructions if yours does not   Now I only had to    download and unpack Eclipse on the server  install X2Go on my local machine  sudo apt-get install x2goclient on Ubuntu   configure the connection  host  auto-login with ssh key  choose to run Eclipse     Everything is just as if I was working on a local machine  including building  debugging  and code indexing  And there are no noticeable lags

User · Answer

This answer currently only applies to using two Linux computers  or maybe works on Mac too --untested on Mac   syncing from one to the other  because I wrote this synchronization script in bash  It is simply a wrapper around git  however  so feel free to take it and convert it into a cross-platform Python solution or something if you wish      This doesn t directly answer the OP s question  but it is so close I guarantee it will answer many other peoples  question who land on this page  mine included  actually  as I came here first before writing my own solution   so I m posting it here anyway    I want to    develop code using a powerful IDE like Eclipse on a light-weight Linux computer  then build that code via ssh on a different  more powerful Linux computer  from the command-line  NOT from inside Eclipse    Let s call the first computer where I write the code  PC1   Personal Computer 1   and the 2nd computer where I build the code  PC2   I need a tool to easily synchronize from PC1 to PC2  I tried rsync  but it was insanely slow for large repos and took tons of bandwidth and data   So  how do I do it  What workflow should I use  If you have this question too  here s the workflow that I decided upon  I wrote a bash script to automate the process by using git to automatically push changes from PC1 to PC2 via a remote repository  such as github  So far it works very well and I m very pleased with it  It is far far far faster than rsync  more trustworthy in my opinion because each PC maintains a functional git repo  and uses far less bandwidth to do the whole sync  so it s easily doable over a cell phone hot spot without using tons of your data    Setup    Install the script on PC1  this solution assumes   bin is in your  PATH    git clone https   github com ElectricRCAircraftGuy eRCaGuy dotfiles git cd eRCaGuy dotfiles useful scripts mkdir -p   bin ln -s    PWD  sync git repo from pc1 to pc2 sh    bin sync git repo from pc1 to pc2 cd    cp -i  sync git repo    sync git repo  Now edit the     sync git repo  file you just copied above  and update its parameters to fit your case  Here are the parameters it contains     The git repo root directory on PC2 where you are syncing your files TO  this dir must  already exist     and you must have  already  git clone d  a copy of your git repo into it    - Do NOT use variables such as   HOME   Be explicit instead  This is because the variable expansion will      happen on the local machine when what we need is the variable expansion from the remote machine  Being      explicit instead just avoids this problem  PC2 GIT REPO TARGET DIR   home gabriel dev eRCaGuy dotfiles    explicitly type this out  don t use variables  PC2 SSH USERNAME  my username    explicitly type this out  don t use variables PC2 SSH HOST  my hostname        explicitly type this out  don t use variables  Git clone your repo you want to sync on both PC1 and PC2  Ensure your ssh keys are all set up to be able to push and pull to the remote repo from both PC1 and PC2  Here s some helpful links    https   help github com en github authenticating-to-github connecting-to-github-with-ssh https   help github com en github authenticating-to-github generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent  Ensure your ssh keys are all set up to ssh from PC1 to PC2  Now cd into any directory within the git repo on PC1  and run    sync git repo from pc1 to pc2  That s it  About 30 seconds later everything will be magically synced from PC1 to PC2  and it will be printing output the whole time to tell you what it s doing and where it s doing it on your disk and on which computer  It s safe too  because it doesn t overwrite or delete anything that is uncommitted  It backs it up first instead  Read more below for how that works     Here s the process this script uses  ie  what it s actually doing    From PC1  It checks to see if any uncommitted changes are on PC1  If so  it commits them to a temporary commit on the current branch  It then force pushes them to a remote SYNC branch  Then it uncommits its temporary commit it just did on the local branch  then it puts the local git repo back to exactly how it was by staging any files that were previously staged at the time you called the script  Next  it rsyncs a copy of the script over to PC2  and does an ssh call to tell PC2 to run the script with a special option to just do PC2 stuff  Here s what PC2 does  it cds into the repo  and checks to see if any local uncommitted changes exist  If so  it creates a new backup branch forked off of the current branch  sample name  my branch SYNC BAK 20200220-0028hrs-15sec  lt -- notice that s YYYYMMDD-HHMMhrs--SSsec   and commits any uncommitted changes to that branch with a commit message such as DO BACKUP OF ALL UNCOMMITTED CHANGES ON PC2  TARGET PC BUILD MACHINE   Now  it checks out the SYNC branch  pulling it from the remote repository if it is not already on the local machine  Then  it fetches the latest changes on the remote repository  and does a hard reset to force the local SYNC repository to match the remote SYNC repository  You might call this a  hard pull   It is safe  however  because we already backed up any uncommitted changes we had locally on PC2  so nothing is lost   That s it  You now have produced a perfect copy from PC1 to PC2 without even having to ensure clean working directories  as the script handled all of the automatic committing and stuff for you  It is fast and works very well on huge repositories  Now you have an easy mechanism to use any IDE of your choice on one machine while building or testing on another machine  easily  over a wifi hot spot from your cell phone if needed  even if the repository is dozens of gigabytes and you are time and resource-constrained    Resources    The whole project  https   github com ElectricRCAircraftGuy eRCaGuy dotfiles   See tons more links and references in the source code itself within this project   How to do a  hard pull   as I call it  How do I force  quot git pull quot  to overwrite local files    Related    git repository sync between computers  when moving around

User · Answer

Try the Remote System Explorer  RSE   It s a set of plug-ins to do exactly what you want    RSE may already be included in your current Eclipse installation  To check in Eclipse Indigo go to Window   Open Perspective   Other    and choose Remote System Explorer from the Open Perspective dialog to open the RSE perspective   To create an SSH remote project from the RSE perspective in Eclipse    Define a new connection and choose SSH Only from the Select Remote System Type screen in the New Connection dialog  Enter the connection information then choose Finish  Connect to the new host   Assumes SSH keys are already setup   Once connected  drill down into the host s Sftp Files  choose a folder and select Create Remote Project from the item s context menu   Wait as the remote project is created     If done correctly  there should now be a new remote project accessible from the Project Explorer and other perspectives within eclipse  With the SSH connection set-up correctly passwords can be made an optional part of the normal SSH authentication process  A remote project with Eclipse via SSH is now created

User · Answer

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

User · Answer

For this case you can use ptp eclipse https   eclipse org ptp  for source browsing and building   You can use this pluging to debug your application  http   marketplace eclipse org content direct-remote-c-debugging

User · Answer

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

[c] Work on a remote project with Eclipse via SSH

Examples related to c

Examples related to eclipse

Examples related to ssh

Examples related to eclipse-cdt

Examples related to remote-debugging