[CMake] Private dependencies of static libraries exported as targets

[Ivan Shapovalov]

TBH, I do not see the "PRIVATE dependencies are made PUBLIC for the
purposes of linking when the dependent is static library" there.

-- 
Ivan Shapovalov / intelfx /


On 2016-08-16 at 02:35 -0500, Nicholas Braden wrote:
> Yes, the behavior is documented in several places, the most prominent
> being here:
> https://cmake.org/cmake/help/latest/manual/cmake-buildsystem.7.html#t
> ransitive-usage-requirements
> 
> 
> On Mon, Aug 15, 2016 at 9:22 PM, Ivan Shapovalov <intelfx at intelfx.nam
> e> 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 /
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://public.kitware.com/pipermail/cmake/attachments/20160817/98ffd672/attachment.sig>