Error building on Windows

[Xiot]

The build script fails in a couple places while attempting to run make on windows.

Here is what I get.

Python

$ make buildp
Building python...
Obtaining file:///D:/Development/Git%20Hub/js/js-beautify/python
Requirement already satisfied (use --upgrade to upgrade): six>=1.6.1 in c:\program files\python27\lib\site-packages (from jsbeautifier==1.5.5)
Installing collected packages: jsbeautifier
  Running setup.py develop for jsbeautifier
    Creating c:\program files\python27\lib\site-packages\jsbeautifier.egg-link (link to .)
    Removing jsbeautifier 1.5.5 from easy-install.pth file
    Adding jsbeautifier 1.5.5 to easy-install.pth file
    Installing js-beautify script to C:\Program Files\Python27\Scripts
    Installed d:\development\git hub\js\js-beautify\python
Successfully installed jsbeautifier-1.5.5

$ make testp
Testing python implementation...
Python 2.7.8
./jsbeautifier/tests/shell-smoke-test.sh: line 2: $'\r': command not found
: No such file or directorysmoke-test.sh: line 4: cd: ./jsbeautifier/tests
./jsbeautifier/tests/shell-smoke-test.sh: line 5: $'\r': command not found
./jsbeautifier/tests/shell-smoke-test.sh: line 6: syntax error near unexpected token `$'\r''
'/jsbeautifier/tests/shell-smoke-test.sh: line 6: `test_cli_common()
Makefile:32: recipe for target 'testp' failed
make: *** [testp] Error 2

Javascript

$ make buildj
Building javascript...

$ make testj
Testing javascript implementation...
v0.12.0

> js-beautify@1.5.5 test D:\Development\Git Hub\js-beautify
> ./js/test/shell-smoke-test.sh

'.' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! Test failed.  See above for more details.
Makefile:39: recipe for target 'testj' failed
make: *** [testj] Error 1

I can succesfully test the javascript by running node ./js/test/node-beautify-tests.js directly

These were all run from within Cygwin

[bitwiseman]

I think the error is that make on windows doesn't process the #! at the start of the file.

[Xiot]

Ya, windows doesn't deal with those.
Could you move it to a js script that gets run by node and just spawn the python tests from there using something like python-shell?