how to import project from remote location

Mahmood Naderan mahmood.nt at gmail.com
Mon Nov 14 15:25:32 GMT 2011


>The custom buildsystem does not support remote setups, neither does the
>C++ language plugin. Those only work with local projects, in particular
>since parsing would be horribly slow with remote files.

Then it is not possible to find function definitions, variable and
other thing. Is that right?

So what is the pros of loading a remote project?

On 11/14/11, Andreas Pakulat <apaku at gmx.de> wrote:
> On 14.11.11 17:11:18, Mahmood Naderan wrote:
>> fish:// worked thanks.
>>
>> One more question. the project is now loaded from remote location. Is
>> that mean I am working directly on remote files? I mean I change some
>> files and save them. Are they going to replace in remote location
>> directly? or the project is imported to a temp directory in my local
>> machine?
>
> Yes and Yes. That is, fish is implemented via KDE code (kio to be
> precise) which downloads the files that are being opened through ssh,
> stores them into a temporary file and once the temp file is saved it
> uploads everything again to the server. For the user and KDE application
> this is completely transparent and they don't notice anything about this
> - other than the whole saving being slow.
>
>> Also, the parse complains about some costum paths. I added
>> "fish://mahmood@server/home/mahmood/project/src" to the costum path.
>> Is that enough? I see nothing happens and the parse still underline
>> the include paths.
>
> The custom buildsystem does not support remote setups, neither does the
> C++ language plugin. Those only work with local projects, in particular
> since parsing would be horribly slow with remote files.
>
> Andreas
>
>
> _______________________________________________
> kdevelop mailing list
> kdevelop at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop
>


-- 
--
// Naderan *Mahmood;




More information about the KDevelop mailing list