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

List:       kde-buildsystem
Subject:    Re: [PATCH] builds libs by default with full RPATH
From:       Andreas Hartmetz <ahartmetz () gmail ! com>
Date:       2007-12-20 3:22:53
Message-ID: 200712200422.53728.ahartmetz () gmail ! com
[Download RAW message or body]

Am Donnerstag 20 Dezember 2007 04:00:12 schrieb Michael Biebl:
> 2007/12/16, Alexander Neundorf <neundorf@kde.org>:
> > Hi,
> >
> > attached you can find a small patch which changes the default value of
> > the option KDE4_USE_ALWAYS_FULL_RPATH from OFF to ON.
> > A better name for that option would be "KDE_BUILD_LIBS_WITH_RPATH", then
> > I wouldn't have to explain what it does.
> >
> > Pros: libs should always have the correct RPATH
> > Cons: "make install" will take longer, since libs then also have to be
> > relinked (as long as cmake without chrpath support is used)
>
> Hi Alex,
>
> do you know about
> http://people.debian.org/~che/personal/rpath-considered-harmful
> or
> http://wiki.debian.org/RpathIssue
>
> Considering the issues raised there, what's your answer to this?
>
And I might add - why are we using RPATH again? Why are search paths not good 
enough? Do the advantages really outweigh the disadvantages? If yes, is it 
still true if all KDE libraries are installed in /usr/lib as all distros do 
now or will do soon?
Dunno, RPATH looks like an ill-advised hack to me and (IIRC, IMBW, YMMV...) I 
haven't heard very convincing reasons to use it so far.
_______________________________________________
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem
[prev in list] [next in list] [prev in thread] [next in thread]