# How do I pull full paths out of UNRESOLVED\_DEPENDENCIES\_VAR

**URL:** https://discourse.cmake.org/t/how-do-i-pull-full-paths-out-of-unresolved-dependencies-var/1945
**Category:** Code
**Created:** [September 29, 2020, 6:49pm UTC](https://discourse.cmake.org/t/how-do-i-pull-full-paths-out-of-unresolved-dependencies-var/1945 "2020-09-29T18:49:32Z")
**Posts on this page:** 1
**Showing post:** 2

<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: [September 29, 2020, 11:14pm UTC](https://discourse.cmake.org/t/how-do-i-pull-full-paths-out-of-unresolved-dependencies-var/1945/2 "2020-09-29T23:14:17Z")

</div>

They’re unresolved because it is unknown where they live. Otherwise they’d be in `RES` in your example 🙂 .

As for the `ms-api-` and other similar DLLs, these are “fake” DLLs and are a technique Microsoft is using to make ABI compatibility more granular (instead of a single massive MSVCRT DLL). See the discussion [here](https://discourse.cmake.org/t/get-runtime-dependencies-has-difficulties-with-windows-api-sets/1768) for more details on it and a potential mechanism CMake can provide to help users out with these specific DLLs.

Cc: @kyle.edwards

---

_[View the full topic](https://discourse.cmake.org/t/how-do-i-pull-full-paths-out-of-unresolved-dependencies-var/1945)._