lib or lib64?
Alexander Neundorf
neundorf at kde.org
Fri Feb 15 20:52:31 UTC 2013
On Friday 15 February 2013, Treeve Jelbert wrote:
> I am trying to keep my qt5 related stuff separate from the qt4 stuff,
> so qt5 in installed to /opt/qt5.
>
> The qt5 build process installs the libraries, cmake and pkgconfig stuff
> to /opt/qt5/lib.
>
>
> attica5, strigi-5 and phonon4qt5 install to /opt/qt5/lib64
>
> $ ls /opt/qt5/lib64
> cmake libphonon4qt5.so.4
> libstreamanalyzer.so.0.7.8
> libattica.so libphonon4qt5.so.4.6.60
> libstreams.so
> libattica.so.0.4 libsearchclient
> libstreams.so.0
> libattica.so.0.4.1 libsearchclient.so
> libstreams.so.0.7.8
> libphonon4qt5experimental.so libsearchclient.so.0
> pkgconfig
> libphonon4qt5experimental.so.4 libsearchclient.so.0.7.8 strigi
> libphonon4qt5experimental.so.4.6.60 libstreamanalyzer.so
> libphonon4qt5.so libstreamanalyzer.so.0
>
> libdbusmenu-qt5 installs to /opt/qt5/lib
>
> kf5libs installs to /opt/qt5/lib
>
> I am using the same cmake commands in all cases.
>
> This becomes rather messy regarding search paths for pkgconfig and
> cmake.
>
>
> How can I force everything into one place?
If you pull a fresh kdelibs, it should now also go into lib64/.
Let me know if it doesn't.
On Debian multiarch should now also be handled properly.
The install dirs are now taken from FindKF5.cmake:
find_package(KF5 ... InstallDirs)
which has code to handle that.
Alex
More information about the Kde-frameworks-devel
mailing list