chalet-org
Native compile strategy: header dependencies
No dependency management yet at all. At the moment, the native-experimental strategy is used as the default in CI builds since deps are not needed there, but locally, it's not really a viable option.
The way to do this I think would be to read through all the *.d files and consolidates them to a single list, goes through the list, gets the timestamp for each file, then compares them with the previous timestamp.
MSVC: *.d files have to be parsed from /showIncludes
Noticed Ninja has a long pause when it's spun up after several files w/ headers are changed. If it's not just a huccup (although it's happened multiple times), it's probably crawling dependencies at that time - immediate files that were changed, then their dependants
Poor choice of words in the title -- this is referring to individual cpp file dependency checking (getting a list of headers) in the "native" build strategy (ie. without ninja/makefile behind the scenes).
At the moment, you can invoke vcpkg and Conan with process targets, but integration with those isn't really planned. The main issue is getting the toolchain info to the package managers and ensuring they work with the build. vcpkg is probably the most likely of the two to get integrated.
Questions like this should go in discussions though.