[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 88182] New: Host compiler configuration is wrongly part of the project configuration
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2004-08-26 23:53:06
Message-ID: 20040826235306.23772.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=88182      
           Summary: Host compiler configuration is wrongly part of the
                    project configuration
           Product: kdevelop
           Version: unspecified
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: iztok.kobal sysen si


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.


[prev in list] [next in list] [prev in thread] [next in thread]