Use DEPFILE instead of implementing a custom parser?

[nextsilicon-itay-bookstein]

It seems that cython has a --depfile argument and cmake's add_custom_command has a DEPFILE argument meant for this sort of thing. I'm not aware of the historical context, but perhaps replacing the custom regex parsing logic in UseCython.cmake with the DEPFILE functionality would both reduce maintenance burden and increase robustness?

[jcfr]

Thanks for the suggestion, in the process of consolidating and revisiting the module implementation, will definitely look into it.

Final work will be hosted into scikit-build/cython-cmakerepository.

[nextsilicon-itay-bookstein]

Cool. It's actually useful for me to have that broken out to a separate repository as well, as I've recently written cmake code to replace the python-driven build machinery (which is otherwise completely opaque to the cmake dependency graph, and rebuilds native libraries I've already built in a nested cmake invocation).