Let's say I have many different potential names for a library and the
following filesystem
/usr/lib/libnspr4.so
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4a.so
find_library(TEST_LIBRARY
NAMES nspr4 nspr4a
HINTS ${CMAKE_CURRENT_SOURCE_DIR}
)
I'm somewhat surprised that the following code finds
On 8. Sep, 2010, at 8:25 , Philip Lowman wrote:
Let's say I have many different potential names for a library and the
following filesystem
/usr/lib/libnspr4.so
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4a.so
find_library(TEST_LIBRARY
NAMES nspr4 nspr4a
HINTS ${CMAKE_CURRENT_SOURCE_DIR}
Wow, that's pretty bad. I even replied to one of those threads. Sorry for
the noise. The official bug post for this issue is here:
http://public.kitware.com/Bug/view.php?id=10718
I agree with Alan Irwin that it will continue to haunt users well into the
future.
On Wed, Sep 8, 2010 at 2:38 AM,
On 09/08/2010 08:38 AM, Michael Wild wrote:
On 8. Sep, 2010, at 8:25 , Philip Lowman wrote:
Let's say I have many different potential names for a library and the
following filesystem
/usr/lib/libnspr4.so
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4a.so
find_library(TEST_LIBRARY
NAMES nspr4
On Wed, Sep 8, 2010 at 8:56 AM, Michael Hertling mhertl...@online.dewrote:
...which shows that 10718 is still alive. ;-)
Hi Philip,
what's your opinion on this topic, in particular
- swapping loops and the required effort, the related risks
and the expected results,
I'd like to know if