Qt Creator: Remote Development (via SSH) for "Desktop" projects?
-
I believe the only solution to get a good development environment is to use x forwarding, but if your link is not fast enough it will not be usable. So my second choice would be to mount the remote filesystem and the include/library path so to create a kind of sendbox where I can work locally having all the files remotely. Another possibility is to setup a virtual machine that is configured as the remote target machine and finally the last solution is to use a tool for filesystem sync (DVCS or VCS or even an ad-hoc script) and compile on the remote machine via terminal emulation. It would not be hard after all, thanks to (q)make, but it will become more difficult to debug.
-
Why forward X when he can start vnc server, even if the machine doesn't run in graphical mode. Using vnc server and accessing via vnc viewer would allow him to reconnect and continue working even if the connection drops.
Other thing could be to start a version/revision control system on the server and update it with the needed data, then compile via the ssh link he has. Qt Creator already has integration with Bazaar, Mercurial and Git, so I think that would be the best solution in this case.
-
Hi all,
Thanks for the advice. The link is slow but the bigger issue is latency and jitter, so remote desktop anything is not going to work.
I see that NetBeans has some capability for remote c/c++ development via SSH. Somehow it picks up include paths, etc via the remote shell connection.
See: http://netbeans.org/kb/docs/cnd/remotedev-tutorial.html
NetBeans even has rudimentary Qt support, but I'd much rather use Qt Creator.
Is this kind of setup possible with Qt Creator? If not, is it on the feature map? (Seems like it'd be helpful for developing Mobile apps with real HW too.)
Thank you
-
Helo,
Have you made any progress? I am trying to do the same thing but I am slowly loosing the will. Atm I have tried lunching gdbserver process on my centos 6 remote server and tried connecting via QtCreator remote debugging tool on my local Ubuntu development machine. Debugger starts but it soon fails saying no executable given. So I mounted folder containing binary I wish to debug from remote server and finally got error about miss matching libs. From this point on I'm lost.
I also tried remote development from eclipse, established eclipse connection using ssh and creating remote C/C++ project which even builds if I create makefile by my own but eclipse doesn't recognizes binary so I can't even run/debug it using eclipse (works via terminal). Tried given binary parsers without success. I also think this is the only way this thing will work since it uses remote compiler and library's.
I am thinking of creating virtual machine with same setup on my centos 6 remote machine and remote debugging from it, but I'm afraid even then I will get some kind of lib version miss matches since server doesn't have X installed.
Tomorrow I will carefully read all the replays and try them out.
-
There is also sshfs which can mount directories from a remote machine via SSH. That could get access to the sources. Not sure how the filesystem will impact performance.
-
Hi All,
sorry for reviving this old thread. I am also interested in using qt creator as an IDE for remote projects. Have there been any updates in this direction?Btw. I recently came across the Visual Studio C++ for Linux Development Extension which seems like a good alternative for windows based developers. However, I'd love to be able to stick with QtCreator.
Best,
David -
I decided to switch to vim just for that one reason. After some steep learning curve, I'm almost there... my new workflow is now tmux + vim.
Despite the added benefits of working remotely I do miss the features provided by qtcreator: completion, search and replace, debug, build, jump to build errors, etc... even though some/all of that is supposedly possible with vim :( -
Hi. I've been working with QtCreator since it's very early days. I was used to all the goodies of this IDE. Then I had to compile and develop in the LLVM source tree and I didn't want to give up on that IDE approach. Compiling LLVM on my machine is way too slow. That's why I switched to compiling on a machine that has more power. Now, compiling is fine but editing is harder for me because I'm used to the IDE. I tried out VScode about a year ago and it wasn't that good either. But nowadays I can highly recommend VSCode for editing CMake projects over SSH without x-forwarding. For x86_64 and for Apple this works great and the IDE has improved very much since last year. There's a bit more tinkering involved but that's fine for me.
