> But a quick check of your link above shows no comments or anything
> in the makefile describing what it does,
Thanks for your look at my example.
> and I don't really understand the purpose behind all these recipes
> which consist of if-statements where the body of the recipe is made empty
> if variables are not set.
It is my approach for recipe execution guards. I hope that such conditions
are sufficient to let the affected recipes only run for a single target
despite of the specification of several output files there.
Some targets will not usually work together with the make command-line
option "-j" if a corresponding value was passed that is greater than one
for such a parameter.
> I will also mention that I see you using various bash-specific shell
> features (e.g., 'XY=$${XY/|/ }'), but I don't see any setting of "SHELL
> = /bin/bash" in your makefile; unless you do this then your makefiles
> will fail on any system where /bin/sh (which is the default setting for
> SHELL in make) is not bash;
Thanks for your reminder.
Are there any more programs which support text replacement within content
from "shell variables" directly?
Regards,
Markus
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
