# Why is my library consumer getting a PRIVATE library dependency

**URL:** https://discourse.cmake.org/t/why-is-my-library-consumer-getting-a-private-library-dependency/5776
**Category:** Usage
**Created:** [June 1, 2022, 6:50pm UTC](https://discourse.cmake.org/t/why-is-my-library-consumer-getting-a-private-library-dependency/5776 "2022-06-01T18:50:15Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![JRR](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/j/ecccb3/32.png) [@JRR](https://discourse.cmake.org/u/JRR)
#### Post date: [June 1, 2022, 7:54pm UTC](https://discourse.cmake.org/t/why-is-my-library-consumer-getting-a-private-library-dependency/5776/3 "2022-06-01T19:54:33Z")

</div>

Thanks @ben.boeckel. I found the entries doing a google search

```auto
"compile_only" inurl:discourse.cmake.org

```

The discussion for [Add only library headers during target\_link\_libraries()](https://discourse.cmake.org/t/add-only-library-headers-during-target-link-libraries/2973) from 3/2021 is pretty much exactly what I’m wanting.

I also see a workaround in [Idiomatic way to deal with huge number of include directories](https://discourse.cmake.org/t/idiomatic-way-to-deal-with-huge-number-of-include-directories/3947), although it means creating two libraries for this, still it’s a step forwards.

Thank you!

---

_[View the full topic](https://discourse.cmake.org/t/why-is-my-library-consumer-getting-a-private-library-dependency/5776)._