Host compiler configuration is wrongly part of the project configuration

[Iztok Kobal]

In KDevelop-2.1.x one could configure compilers (this refers to native 
(cross-)compilers like C, C++, fortran etc. and not to e.g. Java 
bytecode compiler) for diferent hosts (i686-linux, arm-linux, ppc-linux 
etc) using the Options->KDevelop Setup->Compiler dialog to keep the 
project settings independent from the developer's enviroment/KDevelop 
settings.

It is not possible with the KDevelop-3.x anymore. Compiler command 
definition (at least for C/C++ projects) is now part of the Project 
(Project->Project Options->Configure Options->some 
configuration->Compiler Command) which I consider highly invalid. 
Namely, it forces the whole development team to have exactly the same 
development enviroment, file-system-wise. Which, of course, is at least 
naive to be expected to be achieved and maintained.

I would expect similar compiler configuration as it was with 
KDevelop-2.1.x, that is, the pairs foo-linux-somecompiler and 
appropriate compiler path being part of the 
$(HOME)/.kde/...../config/kdeveloprc or some other private configuration 
file.

I've alos posted the bug report 
(http://bugs.kde.org/show_bug.cgi?id=88182) which opens the problem of 
the compiler location configuration within the KDevelop-3.x. I remember 
the matter being discussed some time ago in KDevelop-devel or 
kde-mail-kde-org maillists where also F at lk pointed out that this was 
solved better in KDevelop-2.

I have also browsed the KDevelop-3 user manual which confirmed my 
knowledge of the matter and it does not suggest anything better than 
including full compiler paths into the project configuration instead of 
some kind of Kdevelop local/enviroment configuration.

So, is there something going on on this bug/enhancement/matter or is it 
meant to be solved different way or simply nobody have been thought 
about it to-date ?

Regards, Iztok