[cmake-developers] The lib64 case

[Alexander Neundorf]

On Saturday 24 March 2012, Rolf Eike Beer wrote:
> 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. 

Just be careful not to break any modules while doing this.
"break" here means that if some file was found before, it still must be found 
after the change, no matter in which strange setup this was.

An update of cmake must not break any existing builds out there.

Alex