# RPATH not set, but necessary

**URL:** https://discourse.cmake.org/t/rpath-not-set-but-necessary/861
**Category:** Code
**Tags:** os:macos
**Created:** [March 25, 2020, 5:51pm UTC](https://discourse.cmake.org/t/rpath-not-set-but-necessary/861 "2020-03-25T17:51:50Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.cmake.org/u/ben.boeckel)
#### Post date: [March 26, 2020, 2:44pm UTC](https://discourse.cmake.org/t/rpath-not-set-but-necessary/861/9 "2020-03-26T14:44:53Z")

</div>

Yeah, the need to have a usage requirement pierce`PRIVATE` dependencies for those that impose requirements on any end binary in the chain (`EXECUTABLE` or possibly a `MODULE`). I don’t know of the best way to do it.

`$<LINK_ONLY:>` can remove the interface or compile usage requirements at least.

---

_[View the full topic](https://discourse.cmake.org/t/rpath-not-set-but-necessary/861)._