Fix developer setup section for windows #5342
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contributor checklist:
development
branchyarn ready
run passes successfully (more about tests here)Description
This PR references a post (Building with vs2015 fails) on the community forum. While researching the issue i found multiple people having problems with https://github.com/felixrieseberg/windows-build-tools (e.g. felixrieseberg/windows-build-tools#252, felixrieseberg/windows-build-tools#251, felixrieseberg/windows-build-tools#172). According to the commits the project switched to Python 3, but it seems like there has not been a release since and the project seems to be unmaintained. The workaround mentioned in my community forum post (partially sourced from felixrieseberg/windows-build-tools#172) seems overly complicated and installing the two dependencies manually more reasonable to me.
Removes reference to https://github.com/felixrieseberg/windows-build-tools.
Added "Download Build Tools for Visual Studio" and "Download Python 3" as steps.
The PR might also fix/ would have prevented some of the issues that holahila is having on the community forum (I get an error when I run the command “yarn install –frozen-lockfile”), but I'm not sure.
The old setup instructions failed on multiple Windows 10 machines, I verified the new procedure on a fresh installation.