Building and installing processes

[Aleix Pol]

Hi co-kdevelopers,
Right now our IProjectBuilders have an IPB::build and an IPB::install.
It works great, but it has some small integration problems for us
(cmake).

When you install, you first build then install, but cmake does first
the build then build+install. So the first part can be omitted. Also
this generates 2 output views so you don't get to see the warnings.

So I was thinking of solutions, I see two of them, you guys tell me
what's your opinion:
 - We create a new interface based on flags and we make
IProjectBuilder to implement it so that the MakeBuilder (or others)
don't stop working.

class IProjectBuilder2 {
 enum Action { Prune, Configure, Build, Install, Clean, ... };
 Q_FLAGS(Action,Actions)

 virtual KJob* retrieve(Action*) = 0;
};
//this could be a bit tricky to have implemented

 - We extend IProjectBuilder with KJob* IPB::buildAndInstall(item).
This one could internally generate a KCompositeJob by default to
maintain source compatibility.

Thoughts?
Aleix