-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Executing build\all.py on a clean clone fails #526
Comments
Looks like python 3 is being invoked for gjslint. @sandersaares, can you confirm if We have 'python' hard-coded into the command lines of two of our build steps:
Perhaps those should say python2, specifically. @sandersaares, please try changing those to python2 and see if it resolves your issue. |
I confirm modifying these lines to explicitly reference Python 2 does help the build process move forward. As I believe there is no standard way to choose which version of Python to run (they all come as python.exe by default), I imagine the best fix would be to always run the same Python executable that is always running, e.g. from However, now it fails with the following output:
I also tried upgrading my Python 2 but this changed nothing. New version is: Exploring what the script does, it appears to be executing Is Windows supported as a development platform? |
Window is supported, but we don't test the Windows build often enough. We'll fix it. Thanks for the report! |
* Node binaries should have .cmd appended to file name. * htmlhint cannot find .htmlhintrc file. * Use same python environment for subprocesses. Closes #526 Change-Id: I6b4c898b39a3e2eb8d808feb2b46b79fba5dc455
b612704 (latest master branch)
Cloned repository.
Executed
npm install
Executed
python27 build\all.py
Environment is Windows 10, with "Python 2.7.10 (default, May 23 2015, 09:44:00) [MSC v.1500 64 bit (AMD64)] on win32"
A successful build process.
The text was updated successfully, but these errors were encountered: