why "make install" now takes longer and what you can do about it

[Robert Knight]

Hi,

> This way they get the correct libraries when they are used by an
> executable which is executed from the build tree.

Is there an option to avoid using RPATH completely?

The use case I have in mind is switching between qt-copy and the
latest Qt 4.4 snapshots when running applications - in which case I
would like to set LD_LIBRARY_PATH to determine which Qt libraries are
picked up.

At the moment I do this by corrupting the hardcoded path string inside
the binary so that the linker falls back to LD_LIBRARY_PATH.

Regards,
Robert.

On 19/12/2007, Alexander Neundorf <neundorf at kde.org> wrote:
> Hi,
>
> I committed a change to our cmake files, so that now by default also shared
> libraries and plugins are built with the RPATH/RUNPATH pointing to the build
> directory. This way they get the correct libraries when they are used by an
> executable which is executed from the build tree.
> When installing these libs, the RPATH has to be modified to the correct RPATH
> for the install location, it may no longer point to the build tree but must
> point to the install dirs.
> This means with cmake 2.4.x on ELF systems (Linux, BSD, Solaris) the libraries
> will be linked again with the new RPATH - this unfortunately takes some time,
> but we have correct RPATHs now.
>
> There are two things you can do to avoid this:
> -disable the option KDE4_USE_ALWAYS_FULL_RPATH , then you will have the old
> behaviour back
> OR
> -use cmake cvs from today and also current kdesupport, then the RPATH will be
> changed using the chrpath tool, this avoids the need for linking the libs and
> executables again.
>
> Alex
>
>