Version: 3.0.90-CVS (using KDE KDE 3.2.0) Installed from: Compiled From Sources Compiler: gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) OS: Linux The new project wizard insists on having a local directory to create the project in (and there doesn't seem to be any other way to create a project), even if you give it a perfectly valid url (eg. fish://username@host/path). One could create it locally and copy it over, but this seems to be an unnecessary limitation when ioslaves work so well.
This can't really be classified as a bug when KDevelop wasn't designed to support this. It's a nice idea for future development though. Changing to wishlist.
See also #71318
This in fact is a dupe of #71318 Jens, i somehow fail to understand why this is a wish. Though as you said in the other bug, the real error is that the procedure of creating a project pretends that something is posible which actually isn't (and won't for a while for sure). *** This bug has been marked as a duplicate of 71318 ***
It's a wish in that I'd like it to be possible, even if currently it is not. (#71318 serves as a report on the bug aspect of it).
Recent commits to HEAD might have helped, but unless GNU tools start supporting fish:// I don't see this wish become reality. Maybe you should file a request to the GNU autotools people :)
I'm not sure what the GNU autotools have to do with it, at least as I was using it (which was for a perl project). I don't need compile tools in this case. Would setting the compiler to "ssh user@host gcc ...." work in the c/c++ case? (You can set up ssh to be passwordless in the case that the above wouldn't prompt you for a password/passphrase).
As far as remote compilation goes, you don't need to have remote files -- only a remote compiler. This can be trivially solved with distcc, when you set DISTCC_HOSTS=remotehost without including localhost in the hosts lists. That way your compilation will only be done on the remote machine. I guess this should be closed.
The wish that having a remote project, or remote files in a local project, is still outstanding (and I don't think quite addressed by #71318, which seems to be focused on fixing the "misleading" file dialogs). It's not (just|at all) about remote compilation.