[Bug 78020] New: Build system logic could be separated a bit more

[Kuba Ober]

------- 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=78020      
           Summary: Build system logic could be separated a bit more
           Product: kdevelop
           Version: unspecified
          Platform: RedHat RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-devel kdevelop org
        ReportedBy: kuba mareimbrium org


Version:            (using KDE KDE 3.2.1)
Installed from:    RedHat RPMs

I guess it could be helpful in the long run to separate three things under the current "build system" umbrella:

1. configuration management

2. makefile generation

3. make tool

It's e.g. completely possible to use autoconf as (1), do (2) by hand and use cook as (3).

In case of make, (3) is just make, but (2) could be either qmake or automake (or just plain hand-written). 

And so on.

This is nothing that could be done overnight I'm sure, but I guess some discussion is needed as I believe such a separation would reduce redundant work in maintaining different build systems, as well as make kdevelop more expandable. Myself, for example I'm slowly migrating from qmake/make to cook. There are others who use cook as well, and there are some other build tools out there too. And so on.

Rants/reasonable flames (tm) more than welcome :)

Cheers, Kuba Ober