Good idea...

Do I have to do this for every library that links against this external library?


On 19. Dec, 2009, at 20:24 , Clinton Stimpson wrote:

> 
> I just set the LINK_INTERFACE_LIBRARIES property on shared libraries to 
> eliminate these kinds of dependencies.
> 
> Clint
> 
> On 12/19/2009 11:08 AM, Michael Wild wrote:
>> Hi all
>> 
>> I use ExternalProject to optionally build some dependencies as static 
>> libraries. However, since they are statically linked, I don't install them. 
>> Unfortunately, CMake includes these libraries in the export set through the 
>> IMPORTED_LINK_INTERFACE_LIBRARIES property. Worse, it references the 
>> location in the build tree. How can I prevent this from happening?
>> 
>> What is the "officially" sanctioned way of dealing with libraries built 
>> using the ExternalProject module?
>> 
>> Michael

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to