next: merge build-related commits from master #2058
Conversation
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 <[email protected]> PR-URL: nodejs/node-v0.x-archive#20109
PR-URL: nodejs#2036 Reviewed-By: Alexis Campailla <[email protected]>
PR-URL: nodejs#2036 Reviewed-By: Alexis Campailla <[email protected]>
rvagg
force-pushed
the
next-build-makefile
branch
from
65c2a97
to
ef20349
Compare
|
removed d1a47c987debf5668fd3d22ec2b3f5fa282213df (8e9089a) from the list, it's in the middle of these on |
On upgrading openssl, all symlinks in pulic header files are replaced with nested include files. The issue was raised that installing them leads to lost its references to real header files. To avoid this, all public header files are copied into the `deps/openssl/openssl/include/openssl/` directory. As a result, we have duplicated header files under `deps/openssl/openssl/` but copied files are refereed in build as specified to include path in openssl.gyp. Fixes: nodejs#1975 PR-URL: nodejs#2016 Reviewed-By: Rod Vagg <[email protected]> Reviewed-By: Johan Bergström <[email protected]>
to replace the full src download by node-gyp, using the proper format instead of the full source format PR-URL: nodejs#1975 Reviewed-By: William Blankenship <[email protected]> Reviewed-By: Johan Bergström <[email protected]>
rvagg
force-pushed
the
next-build-makefile
branch
from
ef20349
to
69ada22
Compare
mscdex
added
the
meta
|
Rubber-stamp LGTM. |
|
mergified |
|
I left out dcbb9e1 |
|
Binaries are out for a 3.0-pre-rc here: https://iojs.org/download/next-nightly/v2.3.1-next-nightly20150626a6bc75df31/, got a failure on Windows but I think it's temporary and something related to the signing process and a time server it needs to use for that process so I'm rebuilding those. I'd love to get #2066 in before a proper RC for 3.0 but I know that may be controversial for some. |
|
meh, again http://stackoverflow.com/questions/2872105/alternative-timestamping-services-for-authenticode this isn't the first time I've seen this for http://timestamp.globalsign.com/scripts/timestamp.dll, is it time to switch timestamp services or implement some hacky retry logic? @nodejs/platform-windows |
|
If retrying for ~10secs solves the issue, I am in favor of the hack. |
cherry-picks c0c0d73 4208dc4 c87c34c 8e9089a & 09b2cf4 from
master, requesting they be merged in tonext. Mostly so we can use the newmaketooling for next-nightly and rc builds, also brings in the new headers work so we can be putting header tarballs up as well.