-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
VS 2015 support #2036
VS 2015 support #2036
Conversation
if defined noprojgen goto msbuild | ||
|
||
@rem Generate the VS project. | ||
python configure %download_arg% %i18n_arg% %debug_arg% %nosnapshot_arg% %noetw_arg% %noperfctr_arg% --dest-cpu=%target_arch% --tag=%TAG% |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cherry-picking leftover... %nosnapshot_arg%
should be %snapshot_arg%
Thanks @orangemocha, decided that they belong in a separate commit rather than amending the cherry-pick |
LGTM |
ran another CI against this and got this on win2008 only:
@Fishrock123 you're deep in timers now, does this fit into any existing context we have? I'm not sure if this has shown up before or not. Merging regardless because this is unrelated. |
vcbuild.bat calls python configure before setting GYP_MSVS_VERSION, so SelectVisualStudioVersion (tools\gyp\pylib\gyp\MSVSVersion.py) defaults to 'auto' and selects VS 2005. vcbuild sets the environment in the current shell, so this issue would manifest itself only on the first invocation of the script in any given shell windows. Reviewed-By: Julien Gilli <jgilli@fastmail.fm> PR-URL: nodejs/node-v0.x-archive#20109
PR-URL: nodejs#2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com>
PR-URL: nodejs#2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com>
@rvagg Yes, that happens sometimes. It's a minor bug somewhere very deep in windows libuv that will cause timers to occasionally fire quite early. Or something along those lines anyways. I think @orangemocha knew a bit more. |
Hi sorry, I just got around to installing VS2015 on my desktop yesterday. Nice work! |
PR-URL: nodejs#2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com>
PR-URL: nodejs#2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com>
Yes, that issue has been around for a while and that test is marked as flaky in joyent\node. nodejs/node-v0.x-archive#8960 We have been working on a fix (libuv/libuv#385), but it's still work in progress. |
PR-URL: #2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com>
PR-URL: #2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com>
PR-URL: #2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com>
PR-URL: #2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com>
PR-URL: nodejs#2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com>
PR-URL: nodejs#2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com>
This is a port of nodejs/node@4208dc4 . Original commit message: PR-URL: nodejs/node#2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com> PR-URL: #25857 Reviewed-By: Alexis Campailla <alexis@janeasystems.com>
This is a port of 4208dc4 . Original commit message: PR-URL: nodejs#2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com> This was ported to v0.10 in nodejs/node-v0.x-archive#25857
This is a port of 4208dc4 . Original commit message: PR-URL: #2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com> This was ported to v0.10 in nodejs/node-v0.x-archive#25857 PR-URL: #2843 Reviewed-By: rvagg - Rod Vagg <rod@vagg.org> Reviewed-By: orangemocha - Alexis Campailla <orangemocha@nodejs.org> Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
This is a port of 4208dc4 . Original commit message: PR-URL: nodejs/node#2036 Reviewed-By: Alexis Campailla <alexis@janeasystems.com> This was ported to v0.10 in nodejs#25857 PR-URL: nodejs/node#2843 Reviewed-By: rvagg - Rod Vagg <rod@vagg.org> Reviewed-By: orangemocha - Alexis Campailla <orangemocha@nodejs.org> Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
Continues on from #478 but against master this time
/R=@nodejs/platform-windows