# Where can a project install its CMake modules

**URL:** https://discourse.cmake.org/t/where-can-a-project-install-its-cmake-modules/15304
**Category:** Code
**Created:** [November 13, 2025, 1:43pm UTC](https://discourse.cmake.org/t/where-can-a-project-install-its-cmake-modules/15304 "2025-11-13T13:43:55Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![petk](https://discourse.cmake.org/user_avatar/discourse.cmake.org/petk/32/4555_2.png) [@petk](https://discourse.cmake.org/u/petk)
#### Post date: [July 13, 2026, 7:05pm UTC](https://discourse.cmake.org/t/where-can-a-project-install-its-cmake-modules/15304/13 "2026-07-13T19:05:55Z")

</div>

Yes, this topic is about CMake utility and find modules (\*.cmake files).

For the sake of completeness, I’m also linking another blocker here because CMake projects can’t really use such CMake modules yet future-wise (for CPS installations):

> [@Where can a project install its CMake modules when using CPS](https://discourse.cmake.org/t/where-can-a-project-install-its-cmake-modules-when-using-cps/15515):
>
> This is a follow-up question to [Where can a project install its CMake modules](https://discourse.cmake.org/t/where-can-a-project-install-its-cmake-modules/15304) To briefly describe the issue again: Main project provides CMake modules and configuration that extensions (built as separate projects) need to use. When using package config file(s) this works ok I think and projects then need to find the main package and adjust the CMAKE\_MODULE\_PATH to have access to main project’s CMake modules. What about when a project installs CPS? Where and how could this be then resolved? Is…

(CPS currently doesn’t provide any data placeholders to get some path on the system).

---

_[View the full topic](https://discourse.cmake.org/t/where-can-a-project-install-its-cmake-modules/15304)._