Mathias Fröhlich wrote:
The basic problem is that almost all cmake macros tend to test sideeffects
that in some special cases are related to what you need to test. But only for
special cases.
So testing for the existence of a .so in /usr/lib does in no way tell anything
if you can link with that one...
So, the good old autotools, if you like it or not, tend to test what is
required for exactly that reason. And guess - this works way better than what
cmake does.
Can you describe exactly what you think autotools does here? I guess
most autotools tests use a try-compile to find a library. Is that what
you are referring to?
-Bill
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
