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

List:       kde-release-team
Subject:    Re: RFC: Release Management Going Forward
From:       Nicolas Alvarez <nicolas.alvarez () gmail ! com>
Date:       2011-07-27 22:03:08
Message-ID: j0q1uv$ck7$1 () dough ! gmane ! org
[Download RAW message or body]

Dirk Mueller wrote:
> is there a way to tell it to not run make install after every module? for
> packagers, the step of "make" and "make install" must be completely
> seperate.

No, that's fundamentally impossible. If an app and a library get split, the 
app's buildsystem will expect the library to be compiled *and installed* 
before the app is configured.

To build them in a monolithic tarball again, there are two ways: configure 
lib, compile lib, install lib, configure app, compile app, install app (what 
superbuild does); or *modify* the app's buildsystem to (optionally?) work as 
it did before, grabbing the library from the build directory.

The whole point of superbuild is letting you create a monolithic tarball 
without modifying anything from the individual components being built.

-- 
Nicolas


_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]