# Issue with dependencies propagation when different versions are present

**URL:** https://discourse.cmake.org/t/issue-with-dependencies-propagation-when-different-versions-are-present/10429
**Category:** Usage
**Created:** [March 21, 2024, 2:14pm UTC](https://discourse.cmake.org/t/issue-with-dependencies-propagation-when-different-versions-are-present/10429 "2024-03-21T14:14:50Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![adaldev](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/a/9dc877/32.png) [@adaldev](https://discourse.cmake.org/u/adaldev)
#### Post date: [January 8, 2025, 3:17pm UTC](https://discourse.cmake.org/t/issue-with-dependencies-propagation-when-different-versions-are-present/10429/2 "2025-01-08T15:17:03Z")

</div>

Hi  
I’m still missing a solution.

> 2- override `FindThirdPartyLib` system wide: don’t know how, risk of imposing the wrong logic to unrelated projects

Lead to open this: [Calling CMake "default" Find\<Module\> from a user defined one](https://discourse.cmake.org/t/calling-cmake-default-find-module-from-a-user-defined-one/10723) but I’m really unsure that it could be a solution.

What could be the cleaner way ?

Please keep in mind that an important part of my building process is that the package configuration file creation is automated (in fact, I only need to declare my dependencies with a macro that do a `find_package`, `target_link_libraries` and set appropriate var for listing the dependencies name within the configuration files (those names are passed to `find_dependency`). This design can be improved but my goal is to avoid writing the configuration file manually.

---

_[View the full topic](https://discourse.cmake.org/t/issue-with-dependencies-propagation-when-different-versions-are-present/10429)._