[cmake-developers] The lib64 case

Rolf Eike Beer eike at sf-mail.de
Mon Mar 26 10:46:18 EDT 2012


Brad King wrote:
> On 3/24/2012 12:41 AM, 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.
> Sure.  Please add a reference to the find_library documentation that
> points at the FIND_LIBRARY_USE_LIB64_PATHS global property.  Then
> update the documentation of that property to indicate it is set
> automatically when C, CXX, or Fortran is enabled.

Looking at some of the find modules I wonder if that would break them on 
Windows, as the lib64 thing is not enabled there. FindCUDA explicitely says it 
needs it even on Windows, for e.g. FindDevIL I'm not sure. Neither for the 
others.

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/20120326/c418e9f1/attachment.sig>


More information about the cmake-developers mailing list