João Reis

ARM64 Windows was never enabled by default in the main `node-test-*` jobs. It has been there as an option but has to be explicitly selected. I'm not sure we can...

@dy the problem here is not Python but Visual Studio, it detects another installation is already running. IF you were installing or modifying any edition of VS2017, please wait for...

@felixrieseberg you might not have seen my comment at https://github.com/felixrieseberg/windows-build-tools/pull/84#issuecomment-418952650, I did not receive a notification so GitHub might not have triggered one at all. I'd like to know what...

@felixrieseberg I'm working on the installation process issues you described above, I'll include moving to VS2017 as well.

Some notes about the issues mentioned above: **1. Reading the log files to determine success:** The VS2017 installer creates a new process group to run the actual installation and the...

This might be an issue with `node-gyp` and not `windows-build-tools`. `node-gyp` does not work well with non-ASCII paths: https://github.com/nodejs/node-gyp/issues/1520 . @jimmylab as a workaround, this might work if you find...

As things currently stand, this workaround might work: https://github.com/nodejs/node-gyp/issues/1753#issuecomment-496024604 . Or it might not, it's completely unsupported. @saper please consider removing the requirement for an explicit version of `node-gyp`. If...

I did set up the fanned jobs a long time ago, and I can't say I remember all the details. It's possible that Jenkins artifacts simply didn't have enough functionality...

Published the latest versions: - https://unofficial-builds.nodejs.org/download/release/v19.3.0/ - https://unofficial-builds.nodejs.org/download/release/v18.12.1/ - https://unofficial-builds.nodejs.org/download/release/v16.19.0/ @Macmee we're working towards having ARM64 Windows as an officially supported platform, and then every Node.js version will have ARM64...

ARM64 Windows is officially supported now!