[CMake] Private dependencies of static libraries exported as targets

Nicholas Braden nicholas11braden at gmail.com
Tue Aug 16 03:35:22 EDT 2016


Yes, the behavior is documented in several places, the most prominent
being here:
https://cmake.org/cmake/help/latest/manual/cmake-buildsystem.7.html#transitive-usage-requirements


On Mon, Aug 15, 2016 at 9:22 PM, Ivan Shapovalov <intelfx at intelfx.name> wrote:
> On 2016-08-15 at 21:46 -0400, Guillaume Dumont wrote:
>> As far as I know the PRIVATE
>> keyword
>> should have no effect on transitive linking when foo is static and we
>> call:
>>
>> target_link_libraries(foo PRIVATE bar)
>>
>> Hope this helps.
>
> Wow. I did not know that. Should've tested on sample project.
> It does not solve include path bloat though, but that's a minor issue.
>
> One question remains... is this behavior documented somewhere?
>
> Anyway, huge thanks,
> --
> Ivan Shapovalov / intelfx /
> --
>
> 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:
> http://public.kitware.com/mailman/listinfo/cmake


More information about the CMake mailing list