Follow-up Comment #1, bug #40503 (project make):
Detection of Unix scripts with shebang is a compatibility feature, meant for
running Makefile's that invoke Unix shell scripts. On Unix, what follows the
shebang is the absolute file name of the interpreter in Unix format, like
"/bin/sh" or "/usr/local/bin/perl". However, it doesn't make sense to use
these absolute file names verbatim on Windows, since the chances of having
/bin or /usr/local/bin directory on every drive are nil. Therefore, Make uses
the reasonable alternative of using the basename of the interpreter's path,
assuming that it will be on PATH.
So far what Make does. I'm not sure what you suggest to do instead, when you
say "same as the logic for recipes". Please elaborate.
In any case, using the whole absolute file name is a non-starter, as it will
punish too many use cases that worked until now. Likewise, this feature will
never use backslashes, since those cannot possibly happen in Unix scripts.
I'm unsure how or why you even have such a script with a shebang.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?40503>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
