Thanks for building GENie. It is very flexible and helpful.
Using genie.exe 1160 on Windows my custombuildtask specifies dependencies. These dependencies can be correctly referenced with $(1) et al. in my custombuildtask commands. However, they do not show up as additional dependencies in vs (2019) code generations.
This is useful if any of multiple files change, triggering a custom build task. This maps to an <AdditionalInputs> field of <CustomBuild> in the vcxproj file.
Alternatively, I noticed additional dependencies are handled as expected in Ninja build files, triggering a remake.
The docs simply say "additional dependencies, that can be used as parameters to commands", so the vs generation is technically correct. :) However, support for this field in vcxproj files would help the program work as anticipated by its users, I suspect.
Thanks for building GENie. It is very flexible and helpful.
Using genie.exe 1160 on Windows my custombuildtask specifies dependencies. These dependencies can be correctly referenced with
$(1)et al. in my custombuildtask commands. However, they do not show up as additional dependencies in vs (2019) code generations.This is useful if any of multiple files change, triggering a custom build task. This maps to an
<AdditionalInputs>field of<CustomBuild>in the vcxproj file.Alternatively, I noticed additional dependencies are handled as expected in Ninja build files, triggering a remake.
The docs simply say "additional dependencies, that can be used as parameters to commands", so the vs generation is technically correct. :) However, support for this field in vcxproj files would help the program work as anticipated by its users, I suspect.