I'm sorry, I'm not sure I understand. In your example, there is target_link_libraries(lib3 PUBLIC lib1). It looks like lib2 has target_link_libraries(lib2 PRIVATE lib1).
http://public.kitware.com/pipermail/cmake/2016-May/063382.html On Thu, May 12, 2016 at 9:10 AM, Patrick Boettcher <patrick.boettc...@posteo.de> wrote: > On Thu, 12 May 2016 09:04:10 -0500 > iosif neitzke <iosif.neitzke+cm...@gmail.com> wrote: > >> target_include_directories(lib1 INTERFACE /tmp) means /tmp is >> propagated with lib1, but not used to build lib1. > > I know. Could you elaborate how this is related with lib3 PRIVATEly linking to > lib1? > > regards, > -- > Patrick. -- 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
