Issue about PRIVATE in target_link_libraries

[ben.boeckel (Ben Boeckel (Kitware))]

@FuXii

Why?

It’s how linking CMake targets works in general. This thread is very similar to your question:

How do I configure a library so that the projects which depend upon it do not need to know about the projects upon which it depends?

I have Project A, a library, and Project B, an executable which depends on A. A and B are completely separate with regard to directory structure, build systems, etc. A depends on a third party library, X. As it happens in my case, A, B, and X all use CMake, but A is the only project under my control. How can I configure CMake for A so that B does not need to know about X? For the moment, B gets a linker error, and the only way that I can find to make that go away is to have B reference X, w…