Hi!
I'm using KDevelop 5 in some projects using custom makefile and it is great!
The issue I've got is that I'm the only one (for now) using KDevelop in my team and I'd like to avoid polluting our sources repository with KDevelop project config files and folders (.kde4).
Is there is a way to keep project files away ?

I'd suggest to simply add them to the ignore list of your version control system.

scummos wrote:I'd suggest to simply add them to the ignore list of your version control system.

I do it - The problem is that whenever I make a fresh checkout from our git repository I need to copy KDevelop config files into checkout sources.
I've created a patch with it to make it easier but it still needs updating and is generally not comfortable.
Generally I'd like to create a project referencing external sources -I was trying to use symbolic links but it was not working perfectly - (like creating new files was not in my sources directory but in Project's directory)).

Before KDevelop I was using intensively Netbeans and there I was able to create such projects with list of external source folders.

What kind of config files do you have in mind? There are not a lot which contain any information, are there?

Generally .kdev4 folder and <project_name>.kdev4 file

Hm, but how much effort is it to set up your project with KDevelop? Usually it's like "click open/import, select folder, done" and KDevelop recreates pretty much exactly the config file you had before ... or what do you need to set up, and why do you need to do it multiple times?

In my case there is much more effort than that - I work with legacy code using custom project (makefile based) and I need to set up many options to make it work for me.
And the problem is that I need to do it quite frequently.

I've been trying to play with symbolic links to project files in my source tree or to source folders from my project - both don't work properly as it seems that KDevelop resolves symbolic links and searches to other files in real project location (for example class browser's don't see my classes from linked folder). Possibly respecting relative paths and symbolic links could solve my problem as then I would create project in separate location and linked my source folders into project.