Fwd: Re: lib or lib64?

[Alexander Neundorf]

On Saturday 16 February 2013, Valentin Rusu wrote:
> On Saturday 16 February 2013 11:50:22 Alexander Neundorf wrote:
> > On Saturday 16 February 2013, Valentin Rusu wrote:
> > > On Friday 15 February 2013 21:52:31 Alexander Neundorf wrote:
> > > > On Friday 15 February 2013, Treeve Jelbert wrote:
> > > > > 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.
> > > 
> > > Well, I think that other packagers/distributions tend to put libraries
> > > corresponding to the CPU architecture in lib. For exemple, my 64bit
> > > archlinux has 64bit libraries in lib and 32bit libraries in lib32.
> > > lib64 is a symlink to lib. Wouldn't it be simpler to just install
> > > libraries to lib instead of lib64? This would be more consistent over
> > > time, in my opinion.
> > 
> > So ArchLinux has /lib64 and /lib32 (or /usr/lib64 and /usr/lib32 ?) and
> > /lib (and /usr/lib ?) are symlinks to one of the two ?
> 
> $ ls -ld /usr/lib*
> drwxr-xr-x 172 root root 122880 Feb 14 22:25 /usr/lib
> drwxr-xr-x  17 root root  20480 Feb  9 10:56 /usr/lib32
> lrwxrwxrwx   1 root root      3 Jan 27 08:29 /usr/lib64 -> lib
> zamox:/home/valentin/Downloads
> $ ls -ld /lib*
> lrwxrwxrwx 1 root root 7 Jan 27 08:29 /lib -> usr/lib
> lrwxrwxrwx 1 root root 7 Jan 27 08:29 /lib64 -> usr/lib

Ah, ok.
I think it should be fine to default to lib64 in this case.
By default you will get a 64bit-build from cmake, and it will go into lib64/. 
Seems ok to me.
(the same logic is also used in GNUInstallDirs.cmake coming with cmake, and I 
think KDEInstallDirs.cmake and GNUInstallDirs.cmake should stay consistent in 
this regard).

Thanks
Alex