CMAKE TARGET LINK LIBRARIES CODE
CMAKE TARGET LINK LIBRARIES MAC

It will not, however, have a dependency on B unless A If otherĬode links directly to A, then it also will have encoded into it aĭependency on A.

CMAKE TARGET LINK LIBRARIES MAC

Information can be inspected with tools like ldd on Linux, otool on Mac and Shared library, then A will have encoded into it a dependency on B.

Now consider the situation for the actual libraries involved. Handled with target_compile_definitions() and target_compile_options(). The situation with compile flags is analogously The target_include_directories()Ĭommand handles this. Through to anything that links only to A. Any PRIVATE header search path for B will NOT be carried Header search paths defined for target B will also apply to anything that Thus, if A links in B either as PUBLIC or INTERFACE, then any If something linksĪgainst A, it will also need any include search paths from B if B is in A's It says that A uses B in its implementation and B isĬonsider first what this means for include search paths. When A links in B as *PUBLIC*, it is essentially a combination of Libraries (I'm probably over-simplifying here, but you get the picture). Implementation itself, it is effectively just a collection of other Another example is where A isĭefined in CMake as an interface library, meaning it has no actual

Through other than by a pointer or reference. To another library but doesn't actually reference the objects on the way OneĮxample of this is an interface library which simply forwards calls along Into A may need to refer to things from B in order to make such calls. In its implementation, but B is used in A's public API. When A links in B as *INTERFACE*, it is saying that A does not use B Would have no idea what SSL implementation (B) is being used by A, nor does Reference any of the internal SSL data structures or functions.

CMAKE TARGET LINK LIBRARIES CODE

A presents a unified interface for client code which does not Use one of a number of different SSL libraries internally (which B An example of this could be a networking library A which can be built to That makes calls into A would not need to refer directly to anything fromī. Implementation, but B is not used in any part of A's public API. When A links in B as *PRIVATE*, it is saying that A uses B in its So hopefully the following is helpful and if I've got something wrong, thenīy all means please point out the inaccuracies. May have been some subtle inaccuracies in some of the discussions so far, From my understanding of things, I think there Hopefully the explanation that follows helps clarify what PRIVATE, PUBLICĪnd INTERFACE mean and do. Next message: Difference between PRIVATE and PUBLIC with target_link_libraries.Previous message: Difference between PRIVATE and PUBLIC with target_link_libraries.Difference between PRIVATE and PUBLIC with target_link_libraries Craig Scott craig.scott at Difference between PRIVATE and PUBLIC with target_link_libraries

Cmake target link libraries