Building and installing processes

[Aleix Pol]

On Fri, Aug 24, 2012 at 7:38 AM, Andreas Pakulat <apaku at gmx.de> wrote:
> Hi,
>
> On Fri, Aug 24, 2012 at 12:28 AM, Aleix Pol <aleixpol at kde.org> wrote:
>> 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.
>
> Why? I just looked at the code and CMakeBuilder::install only calls
> MakeBuilder::install which merely runs "make install".
> CMakeBuilder::install may also run cmake first and that would be a
> possibly separate outputview, but thats a different thing already
> IMHO.
>
> So are you saying that the "install" action first runs
> IProjectBuilder::build and then IProjectBuilder::install? Maybe thats
> a bit too much dependency-management on our side and we should simply
> drop it? After all a build-system is called a build-system because it
> should take care of first building what needs to be built before
> installing it anyway. I'd consider any buildsystem not doing this to
> be broken.
>
> Andreas
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel

What I mean is that "install" itself is building already, so the build
step is redundant, for cmake. We could call install/fast otherwise
(with the make builder).

Aleix