Well spotted, thanks. I replied further down the thread to OP with another option for doing this in Make, if you'd like to spot any bugs in that one too ;)
Yes, I didn't notice that, I should have tested it more thoroughly!
Make works best when there's a simple relation between target filename and the dependency filenames, and when the output filenames are known ahead of time (or are easily derived from a list of inputs).
You can use Make to achieve what you want though, even when the relations are complex. The idiomatic pattern is to dynamically create your dependency lists and include them at runtime. Make supports this as a first-class feature and will handle re-evaluating any rules that are changed every time an included Makefile is (re-)generated.
But if you want to avoid any complex use of Make then you can push a lot of the logic into your script and then just create a timestamp file for each input as a dummy output to represent the fact that the script was run on each input. eg.
This is a much simpler Makefile, but now you need to create the output filename, make the output directory and redirect the script output inside the script itself. The other drawback is that it's harder to use the output file as an input to another rule. You can use the timestamp file as an input but you won't have the actual filename available to send to a command without some more scripting.
Regardless of what power source you use, all of the power going into a datacentre comes out as heat. So even a 1GW solar plant powering an AI datacentre is putting 1GW of heat into the atmosphere.
Is this the whole Makefile? The default target is the first rule that appears in the file which in this case is the DESTINATION rule, so if you just type make then it should work. If make is telling you there's no rule to make the target then you're probably invoking something like make all and you don't have an all target.
When I run it your Makefile with no target, I get this error:
The things I had to change were: In the foreach you need to reference SOURCE as a variable ${SOURCE}. In your recipe you can just create the directory directly from the output filename instead of doing another regex. Lastly, to create all output files you also need to create a default target (eg. all) that depends on all of the output files.
Does anyone want to read this article with me? I'll say the words out loud and you can tell me if I pronounce any of them incorrectly.