[CMake] Linking to a library: libfoo.so vs libfoo.so.1.2

Mathieu Malaterre mathieu.malaterre at gmail.com
Mon May 19 09:32:23 EDT 2008


On Mon, May 19, 2008 at 3:11 PM, Bill Hoffman <bill.hoffman at kitware.com> wrote:
> Mathieu Malaterre wrote:
>
>> Could you please describe *exactly* what you did before posting, so
>> that I can reproduce, I cannot achieve what you declare (cmake 2.4)
>>
>> Linking C executable testuuid
>> /usr/bin/cmake -P CMakeFiles/testuuid.dir/cmake_clean_target.cmake
>> /usr/bin/gcc  -Wall -W   -fPIC "CMakeFiles/testuuid.dir/testuuid.o"
>> -o testuuid -rdynamic -L/lib -luuid -Wl,-rpath,/lib
>> /usr/bin/ld: cannot find -luuid
>>
>>
>> AFAIK, full path is *not* supported (at least not in cmake 2.4)
>>
> 2.6 supports full paths.  There is not a way to do this in 2.4.

Excellent !
Apparently what I was trying to do is unethical, I need to inspect
system and only allow compilation on system that provide the proper
header, instead of relying on backward ABI (function parameter did not
change) compatibility to do the linking.


Thanks anyway,
-- 
Mathieu


More information about the CMake mailing list