-
Notifications
You must be signed in to change notification settings - Fork 1.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
feat: add VCToolsVersion for msvs (#2906) #2910
Conversation
Allows "MSVC Toolset version" <VCToolsVersion> to be specified for VisualStudio platform. Usage example for binding.gyp ``` 'targets': [ { 'configurations': { 'Debug': { "msvs_configuration_attributes": { "VCToolsVersion": "14.36.32532", ```
@rzhao271 @ryzokuken Please review. Would this land in this repo or in https://github.com/nodejs/gyp-next and then get vendored back into this repo? |
PR LGTM. Any change made to a gyp folder in this repo can be backported to gyp-next, whereas any change made to gyp-next would need to wait for another patch release to be brought back to here. At the same time, I've been putting gyp changes in gyp-next first. |
That is as clear as mud to me. |
I recommend first creating this PR in nodejs/gyp-next unless anyone has any objections. |
Thank you all for your advice. I am not yet knowledgeable enough about gyp-next, but I understand that submitting a pull request to gyp-next is the right way to go. I will try my best to submit a pull request to gyp-next. Hopefully this will be reflected in node-gyp as soon as possible. |
I also agree with this approach. The change itself looks good to me. 👍 |
@StefanStojanovic Please go to https://github.com/nodejs/node-gyp/pull/2910/files and in the upper right click on |
@cclauss I thought we were going to make this change in |
Closing this, since nodejs/gyp-next#209 landed. Thank you @tr-takatsuka for the initiative! |
Checklist
npm install && npm test
passesDescription of change
Add the ability to specify the 'MSVC toolset version' <VCToolsVersion> for the VisualStudio platform.
Usage example for binding.gyp
ps. The following FAILED is displayed in npm test, but I think it is unrelated to this case.
Thank you and best regards.