<br><br><div class="gmail_quote">On Wed, Sep 28, 2011 at 2:47 AM, Michael Wild <span dir="ltr"><<a href="mailto:themiwi@gmail.com">themiwi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="h5"><br>
</div>Only if your installation is broken ;-) If the symlink is broken, I<br>
consider this to be a user-error. Period. OTOH, CMake /could/ check<br>
whether the library is a symlink, and if it is, check that it is valid.<br></blockquote><div><br>Oh, no question the installation is broken. I'd just expect find_library to do whatever minimal validation it can easily do and not return invalid cases it can spot - checking for symlink and whether it's valid would catch one general class of error, and perhaps a quick check to see if the file is a binary or a text file would be another. Not perfect, but such tests should be relatively simple and would improve the utility of find_library.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
But how do you test whether a library is "linkable"?<br></blockquote></div><br>Not sure - autoconf has some sort of test that works in at least some cases in their AC_CHECK_LIB macro, but I'm not really clear on what it does. Even if such a test wouldn't catch all cases, mightn't it be useful to fail when available tests do detect a problem?<br>
<br>Cheers,<br>CY<br>