> When A links in B as PRIVATE, it is saying that A uses B in its > implementation, but B is not used in any part of A's public API.
> When A links in B as INTERFACE, it is saying that A does not use B in its > implementation, but B is used in A's public API. > When A links in B as PUBLIC, it is essentially a combination of PRIVATE and > INTERFACE. It says that A uses B in its implementation and B is also used in > A's public API. All totally correct, and that is how visibility for target_link and target_include commands idiomatically should be used, but I don't believe anything in CMake ensures the code architecture adheres to this scheme. -- 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
