[cmake-developers] The lib64 case

Rolf Eike Beer eike at sf-mail.de
Sat Mar 24 00:41:08 EDT 2012


I have seen a strange behaviour on my (openSUSE) Linux host running on AMD64. 
Sometimes during my Find* module tests libraries in /usr/lib64 were not found. 
It took me a while until I noticed what was going on there: 
FIND_LIBRARY_USE_LIB64_PATHS is not set when I used project(... NONE). While 
this sounds logical maybe the find_library() documentation should be updated to 
say that some language needs to be enabled for it to properly work.

While searching the reason of this behaviour I of course did a "git grep 
lib64" and found a bunch of Find* modules that manually specify lib64 as suffix. 
Also most of them also specified "lib" as a path suffix, which is according to my 
understanding totally unneeded as find_library() will automatically add this 
suffix. Am I correct? Then I would go in the next days and throw them both out. 
Is same is true for find_path() and include suffix?

Greetings,

Eike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20120324/4acdd223/attachment.sig>


More information about the cmake-developers mailing list