But I'm on Windows and have dmake via ActiveState's Perl installed, which is trying to use batch as shell-language.

Do you happen to know how I can tell dmake to use it's "bash" emulation?

(I suppose strongly it comes with ActiveState too)

update

I was able to work around that by using git-bash ... But I'm still curios what the canonical approach may be.

But I'm still curios what the canonical approach may be

The win32/makefile.mk (written for dmake) in the perl source contains:

#
# set this to point to cmd.exe (only needed if you use some
# alternate shell that doesn't grok cmd.exe style commands)
#
#SHELL        *= g:\winnt\system32\cmd.exe
[download]

I guess therefore that, in your makefile, you might want something like:

SHELL        *= C:\path\to\your_shell.exe
[download]

Cheers,
Rob

Plz see Re^4: let Makefile.PL to do the Readme file for me -- new target?, maybe my question becomes clearer then.

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}

SHELL
    This macro defines the full path to the executable image to be used as the shell when processing single line recipes. This macro must be defined if recipes requiring the shell for execution are to be used. It is assigned a default value in the startup makefile. Under UNIX this value is /bin/sh. 

Who knows if it is honoured when set as an "env" var.

Thanks ... I know this. :)

The question is which executable to set?

pryrt's example contains shell code and he said it works on Win.

update

> Who knows if it is honoured when set as an "env" var.

yes the ENV is honored, running dmake inside git-bash works.

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}