Bug 88182

Summary:	Host compiler configuration is wrongly part of the project configuration
Product:	[Applications] kdevelop	Reporter:	Iztok Kobal <iztok.kobal>
Component:	general	Assignee:	kdevelop-bugs-null
Status:	RESOLVED FIXED
Severity:	wishlist
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Iztok Kobal 2004-08-27 01:53:03 UTC

Version:            (using KDE KDE 3.2.1)
Installed from:    SuSE RPMs
OS:                Linux

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 achieve and maintain.

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.

Comment 1 Andreas Pakulat 2008-06-29 21:13:35 UTC

The feature still exists but is much more general, you can supply your own <compiler>.desktop files for the compilers to use and install them in <prefix>/share/services. it supports setting the executable as well as arguments.