On Monday 27 June 2011, Rex Dieter wrote:
> On 06/27/2011 02:49 PM, Alexander Neundorf wrote:
> > On Friday 24 June 2011, Nicolas Alvarez wrote:
> > ...
> > 
> >> I tried an ExternalProject-based approach before for kdeedu. The main
> >> inherent and unavoidable disadvantage is that 'make' alone will
> >> *install* the subprojects.
> > 
> > Yes, that's unavoidable.
> > Serious question: is this a problem ?
> > You can still use DESTDIR.
> 
> A little, but I suppose it'll be a little less bad as long as:
> 
> rm -rf $DESTDIR
> make install DESTDIR=$DESTDIR
> 
> still works (later).
> 

Almost.
Since installing happens at buildtime (so depending projects can find their 
dependencies), it's more like:

$ export DESTDIR=/some/path    # <- must be absolute path
$ cmake -DCMAKE_SKIP_RPATH=TRUE .....     # DESTDIR must be also set at cmake
                  # time, so the dependencies are found in DESTDIR
                  # and RPATH has to be disabled completely, because I think
                  # there is no way to get a correct RPATH with using DESTDIR
$ make            # <- builds and installs into DESTDIR


And it will complain 
* if DESTDIR is set, but not an absolute path
* if it changes from cmake-time to build-time and later on
* if DESTDIR is set but RPATH is not disabled

Alex
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team