You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bnoordhuis opened this issue
Jun 1, 2017
· 4 comments
Labels
buildIssues and PRs related to build files or the CI.ltsIssues and PRs related to Long Term Support releases.windowsIssues and PRs related to the Windows platform.
Just to be clear we're talking about native addons support?
SGTM since MS is giving both VS2017 and VS2017 buildtools for free, and they are able to "cross compile" for older Windows versions.
Sounds relevant also to my CTRL-SHIFT-TAB tab nodejs/node-gyp#1212 a.k.a node-gyp@4
refack
added
build
Issues and PRs related to build files or the CI.
lts
Issues and PRs related to Long Term Support releases.
windows
Issues and PRs related to the Windows platform.
labels
Jun 1, 2017
SGTM. I am not even sure whether Microsoft still offers support for VS2013, their support policy is a little obscured thanks to the number of service packs.
buildIssues and PRs related to build files or the CI.ltsIssues and PRs related to Long Term Support releases.windowsIssues and PRs related to the Windows platform.
Continuation of #7989 in a way. See #13263, it turns out that upgrades to V8 requires floating patches to keep addons building with VS 2013.
That is not a good position to be in and not tenable long-term, that's why I propose to raise the baseline to VS 2015 in node 9.
The text was updated successfully, but these errors were encountered: