[Bug 71318] import existing project: network path not allowed (have to choose a directory)

[Daniel Franke]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=71318     




------- Additional Comments From daniel.franke at imbs.uni-luebeck.de  2003-12-29 02:42 -------
No, I don't think you misunderstand me. I'm using kdevelop successfully and without any problems locally and with filesystems mounted via NFS. 

Here again what I tried to do - in more words:
I was granted ssh access to a host where some tools of significance used in my field of research are developed. I checked out these tools from cvs and tried to grasp the interaction of classes and files. As to expect: I failed. I am still as confused as I was before. Next idea: why not using the class browser and all these other features and goodies kdevelop provides instead of grep and less? Project -> Import -> Custom C++ Makefiles … everything seems to be fine so far. Due to kio network transparency is given – great! But then, I was told to that only (local) directories are allowed :(

I didn’t expect kdevelop to handle the customized build process of the tools mentioned – no problem with invoking make or the compiled programs myself (via ssh sesion). I didn’t expect kdevelop to handle remote debugging of the code either, but at least, at least parsing of the files, building a class list, allow to find-in-files, replace, edit the files and so on … I think this should be possible :)

idea: after importing such a remote project, just disable all feature not available – as make, debugging and so on ?!
OR
instead of submitting 'make' - try "ssh [maybe some flags here] user at host make" and again, everything would be fine ?!