[kde-linux] How to build KDE in isolation

[Bram Schoenmakers]

Op zaterdag 20 mei 2006 18:15, schreef Nick Savoiu:
> Hi all,
>
> I'm using an old RedHat 7.2 installation on which I
> want to build KDE 3.5.2 using the konstruct tool.
>
> My main problem is that KDE 3.0.x is already installed
> by default on the machine. Therefore places like
> /usr/local/lib already contain some libkde*.so*
> libraries.
>
> I thought that if I start the konstruct build in an
> environment devoid of any references to /usr/local/lib
> (i.e. a trimmed down set of PATH/LD_LIBRARY_PATH) then
> none of those libraries will be used. Lo and behold
> after the build finished locking the desktop did not
> work. A quick run of
>
>  ldd kdesktop_lock
>
> showed that it was referencing libkde*.so* files in
> /usr/local/lib instead of my installation of 3.5.2.
>
> I did a grep of the makefiles in the konstruct tree
> and quite a few of them reference /usr/local/lib (in
> particular for Freetype and Perl purposes).
>
> Now the question: how can I build KDE such that it
> does not reference libraries outside of the
> directories that I specify?
>
> Thanks,
> Nick

For me, it's sufficient to pass a prefix along the configure script. I don't 
know Konstruct exactly, but there should an option somewhere to install KDE 
in another prefix than /usr/local . Take /opt/kde for example as prefix for 
your 3.5.x build.

Kind regards,

-- 
Bram Schoenmakers
KDE Netherlands (www.kde.nl)

What is mind? No matter. What is matter? Never mind.
(Punch, 1855)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-linux/attachments/20060521/8321e424/attachment.sig>