[CMake] CMake: using dlopen

Konstantin Tokarev annulen at yandex.ru
Sun Jan 7 17:17:44 EST 2018



07.01.2018, 21:13, "Franck Houssen" <franck.houssen at inria.fr>:
> ----------------------------------------
>> De: "Roger Leigh" <rleigh at codelibre.net>
>> À: "Franck Houssen" <franck.houssen at inria.fr>
>> Cc: cmake at cmake.org
>> Envoyé: Dimanche 7 Janvier 2018 18:14:04
>> Objet: Re: [CMake] CMake: using dlopen
>>
>> -------- Original message --------
>> From: Franck Houssen <franck.houssen at inria.fr>
>> Date: 07/01/2018 13:58 (GMT+00:00)
>> To: Roger Leigh <rleigh at codelibre.net>
>> Cc: cmake at cmake.org
>> Subject: Re: [CMake] CMake: using dlopen
>>
>>> OK, thanks. So, I go with: target_link_libraries(main PUBLIC ... ${CMAKE_DL_LIBS})
>>
>> Use PRIVATE if it is not used in any headers--it's an internal implementation detail.
>
> Difference between PUBLIC/PRIVATE has never been clear to me (usually I always use PUBLIC).
> main.cpp includes dlfcn.h and uses it: not sure to get what you meant (PRIVATE is for templates ? when a header include headers ?)

You should use target_link_libraries(A PUBLIC B) if and only if anything that links with library A must also link with library B (usually because B's types are used in public API of A). If A is not a library, there is no difference.

>
>> Regards,
>> Roger
>
> ,--
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake


-- 
Regards,
Konstantin


More information about the CMake mailing list