> Date: Sun, 28 Apr 2013 22:15:11 +0200
> From: Erik Carstensen
> Cc: make-w32@gnu.org
>
> The problem only happens when make attempts to run the command directly
> (short-circuiting cmd.exe). So one workaround might be to quote spaces with
> double quotes instead of backslashes when invoking com
On Sun, Apr 28, 2013 at 7:26 PM, Eli Zaretskii wrote:
> Thanks for the report. (Any real reason to use batch files whose
> names include whitespace?)
>
Yes. I'm working on a make-based system for building add-on modules to a
certain program. The build system is distributed as a Windows install
> Date: Sat, 27 Apr 2013 21:48:54 +0200
> From: Erik Carstensen
>
> I have the following makefile:
>
> SHELL=cmd.exe
> default:
> "a b.bat" xy
> "a b.bat" "x y"
> a\ b.bat xy
> a\ b.bat x\ y
>
> I also have a file 'a b.bat', which contains a single line:
> echo a
