[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [RFH] CMake and /usr/lib64/

Bastian Venthur <venthur@debian.org> writes:

> Goswin von Brederlow schrieb:
>> Bastian Venthur <venthur@debian.org> writes:
>>> Does anybody know how to tell CMake not to use /usr/lib64 but /usr/lib
>>> when building a package on amd64?
>>> My quick and dirty solution to fix #417044 would be a modification in
>>> debian/rules where I move /usr/lib64 to /usr/lib, but it would be
>>> cleaner if CMake could take care of this.
>> Don't. CMake is correct.
>> The primary location for libraries on amd64 is (/usr)/lib64 and you
>> should compile your code for that. Only when packaging you must move
>> files into (/usr)/lib because dpkg can't handle links in one package
>> (libc6) being directories in others.
> If /usr/lib64 would be correct, why does
>   GTK_LIB_DIR return /usr/lib while

Because this one is "buggy".

>   KDE3_LIB_DIR returns /usr/lib64
> on the very same amd64 box? I mean as long as one of them is a symlink
> to the other it's not really false, but CMake could at least try to be
> consistent couldn't it?
>> If you don't compile for /usr/lib64 then you break compatibility with
>> other linux systems.
> Really? Is it safe to assume /usr/lib is correct for every arch Debian
> supports, so I can hardcode it instead of relying on KDE3_LIB_DIR?

So you can become as buggy as gtk and make the problem worse?

Those defines are there for a reason, so you don't have to assume.

> Cheers,
> Bastian


Reply to: