Version: CVS (using KDE Devel) Installed from: Compiled sources OS: Linux After Installing a new test project because I could not run it otherwise I determined where doing the install put the files. I found that the installation put files outside the directory tree of the project -- and in fact really installed them. This is unacceptable behavior. I would have to recommend against using kdevelop in any sort of production development environment, and would have to actually forbid its' installation in any non-development production environment. There is no way a development system should put files outside the area where it is being developed without first having a serious conversation with the programmer about whether that is what the programmer really wants to do. I would fire a programmer who spread their untested code about in this way.
Well. I haven't tested Maksim's suggestion yet, but assuming it works from within gideon making the default configuration append the project directory to KDEDIRS and using --prefix=<project directory> would solve my problem. (But only if gideon sets it up this way for the programmer. Encouraging the programmer to spread their work all over the system is very bad.)