Re: [Module::Build] Does ./Build work on Windows?

[David G. <da...@hy...>]

Andreas J. Koenig wrote:

>   > It's not an aberration -- it's an alternative, or technically a
>   > shortcut. If CPAN.pm is doing the calls, why not use /path/to/perl for
>   > all four when doing a Build.PL installation?  (And do it with the $^X
>   > that called CPAN.pm unless a specifically different perl path is
>   > requested?)
> 
> Because it simply is not very perlish to abandon shortcuts.

That sounds like an excuse.  You want CPAN.pm to call perl on Build.PL 
and for Build.PL to write a Build and Build.bat.  That just means that 
Module::Build will be responsible for figuring out the right perl 
executable and sticking it in the .bat file.  Is that really any 
different than having CPAN.pm just use the same perl executable all the 
way through? CPAN.pm still has to know which perl to call for Build.PL 
and it still has to call "./Build" three times.  All you save is 
sticking the same perl *that you already have* (that ran Build.PL) in 
front of "./Build" each time.  For that savings, you want Module::Build 
to create a Build.bat on windows?

David