ConfigHeader does not automatically register a generated FileSource as a step dependency #16208
Labels
bug
Observed behavior contradicts documented or intended behavior
contributor friendly
This issue is limited in scope and/or knowledge of Zig internals.
zig build system
Milestone
Zig Version
0.11.0-dev.3803+7ad104227
Steps to Reproduce and Observed Behavior
The
cmake
andautoconf
styles ofConfigHeader
take aFileSource
for the input header, and do indeed work with generated files, but they do not automatically add a dependency on the generation step.Expected Behavior
I would expect the dependency to be added automatically, as this is almost certainly the user's intention, and is already done elsewhere in the build script API.
The text was updated successfully, but these errors were encountered: