Re: [cmake-developers] The lib64 case

2012-03-29 Thread Brad King
On 3/28/2012 7:02 PM, Rolf Eike Beer wrote: Ok, I now added this patch also (and improved some others). Please review, The general form of each change looks correct. I did not thoroughly think through each individual change though. Thanks, -Brad -- Powered by www.kitware.com Visit other Ki

Re: [cmake-developers] The lib64 case

2012-03-28 Thread Rolf Eike Beer
Brad King wrote: > On 3/26/2012 11:49 AM, Rolf Eike Beer wrote: > > Thanks, fixed. And added a patch that removes this in a bunch of other > > modules. > Nice. Looks good so far. I noticed in the context of some of your > changes lines like > > /usr/local/lib/fltk2 > /usr/lib/fltk2 > > This

Re: [cmake-developers] The lib64 case

2012-03-26 Thread 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_PA

Re: [cmake-developers] The lib64 case

2012-03-26 Thread Brad King
On 3/26/2012 1:35 PM, Rolf Eike Beer wrote: Well, that is in fact an interesting question. If "/usr" is in the default paths list and "lib" is a default suffix, will specifying "fltk2" as suffix result in /usr, /usr/lib, and /usr/fltk2, or will also /usr/lib/fltk2 be searched. The latter would me

Re: [cmake-developers] The lib64 case

2012-03-26 Thread Rolf Eike Beer
Brad King wrote: > On 3/26/2012 11:49 AM, Rolf Eike Beer wrote: > > Thanks, fixed. And added a patch that removes this in a bunch of other > > modules. > Nice. Looks good so far. I noticed in the context of some of your > changes lines like > > /usr/local/lib/fltk2 > /usr/lib/fltk2 > > This

Re: [cmake-developers] The lib64 case

2012-03-26 Thread Brad King
On 3/26/2012 11:49 AM, Rolf Eike Beer wrote: Thanks, fixed. And added a patch that removes this in a bunch of other modules. Nice. Looks good so far. I noticed in the context of some of your changes lines like /usr/local/lib/fltk2 /usr/lib/fltk2 This pattern can be replaced by PATH_SUFF

Re: [cmake-developers] The lib64 case

2012-03-26 Thread Rolf Eike Beer
Am Montag, 26. März 2012, 11:01:38 schrieb Brad King: > On 3/26/2012 10:49 AM, Rolf Eike Beer wrote: > > For the beginning I added 2 obvious cleanups to the "lib64-cleanup" topic > > on stage. If noone objects I'll merge them to next soon. > > Thanks. In FindBLAS: > > if (WIN32) > set(_l

Re: [cmake-developers] The lib64 case

2012-03-26 Thread Yury G. Kudryashov
Rolf Eike Beer wrote: > ok, I now have: > > find_path(VAR header.h > HINTS /opt/p1 > PATHS /opt/p2 > PATH_SUFFIXES foo) > > This would search in /usr/include, /usr/foo, /opt/p1/foo, /opt/p2/foo, but > neither in /opt/p1/include nor /opt/p2/include. Correct? As far as I understand, it will sea

Re: [cmake-developers] The lib64 case

2012-03-26 Thread Brad King
On 3/26/2012 10:49 AM, Rolf Eike Beer wrote: For the beginning I added 2 obvious cleanups to the "lib64-cleanup" topic on stage. If noone objects I'll merge them to next soon. Thanks. In FindBLAS: if (WIN32) set(_libdir ENV LIB) elseif (APPLE) -set(_libdir /usr/local/lib /usr/l

Re: [cmake-developers] The lib64 case

2012-03-26 Thread Rolf Eike Beer
Am Montag, 26. März 2012, 08:22:22 schrieb Brad King: > 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 no

Re: [cmake-developers] The lib64 case

2012-03-26 Thread Rolf Eike Beer
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: >

Re: [cmake-developers] The lib64 case

2012-03-26 Thread Rolf Eike Beer
Am Montag, 26. März 2012, 08:52:59 schrieb Brad King: > On 3/26/2012 8:28 AM, Rolf Eike Beer wrote: > >> The find_library command automatically searches "lib" under each path > >> in CMAKE_SYSTEM_PREFIX_PATH and CMAKE_PREFIX_PATH. Any path that has > >> "lib" in it will first be transformed to "li

Re: [cmake-developers] The lib64 case

2012-03-26 Thread Brad King
On 3/26/2012 8:28 AM, Rolf Eike Beer wrote: The find_library command automatically searches "lib" under each path in CMAKE_SYSTEM_PREFIX_PATH and CMAKE_PREFIX_PATH. Any path that has "lib" in it will first be transformed to "lib64" when the above property is ON. Using "PATH_SUFFIXES lib64 lib"

Re: [cmake-developers] The lib64 case

2012-03-26 Thread Rolf Eike Beer
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: >

Re: [cmake-developers] The lib64 case

2012-03-26 Thread Brad King
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

[cmake-developers] The lib64 case

2012-03-23 Thread Rolf Eike Beer
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 t