# Proposal: Dependency pre-scanner for generated includes

**URL:** https://discourse.cmake.org/t/proposal-dependency-pre-scanner-for-generated-includes/3558
**Category:** Development
**Tags:** gen:ninja
**Created:** [June 12, 2021, 2:25pm UTC](https://discourse.cmake.org/t/proposal-dependency-pre-scanner-for-generated-includes/3558 "2021-06-12T14:25:28Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![chapuni](https://discourse.cmake.org/user_avatar/discourse.cmake.org/chapuni/32/1555_2.png) [@chapuni](https://discourse.cmake.org/u/chapuni)
#### Post date: [June 15, 2021, 10:00pm UTC](https://discourse.cmake.org/t/proposal-dependency-pre-scanner-for-generated-includes/3558/9 "2021-06-15T22:00:35Z")

</div>

FYI, I found a similar issue.

> [@Automatically detecting generated dependencies](https://discourse.cmake.org/t/automatically-detecting-generated-dependencies/1183/7):
>
> I saw a topic reference this one and I thought I’d suggest some functionality for CMake that would be useful. We couldn’t go with CMake largely because of this problem and instead went with an in-house solution. We can declare virtual header files that the dependency scanner is aware of. These files are not guaranteed to exist during scanning and are not scanned themselves; nonetheless, the proper dependency is made between the source file and the various generated headers. It would be nice if C…

My proposal will help him, but seems too late.

---

_[View the full topic](https://discourse.cmake.org/t/proposal-dependency-pre-scanner-for-generated-includes/3558)._