Skip to content

[22.x] win,build: Fix MSVS v17.14 compilation issue on v22 #58902

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

Closed

Conversation

StefanStojanovic
Copy link
Contributor

This prevents updating VS 2022 to the latest version (v17.14), in the release CI. We had similar issues with few VS updates in the past too (17.10 and 17.12 IIRC.

Fixes: #58801

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/security-wg
  • @nodejs/v8-update

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. v22.x Issues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch. v8 engine Issues and PRs related to the V8 dependency. labels Jun 30, 2025
Copy link
Member

@targos targos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you update the embedder string in common.gypi?
I assume this also works with previous versions of MSVC.

@StefanStojanovic
Copy link
Contributor Author

Can you update the embedder string in common.gypi?
I assume this also works with previous versions of MSVC.

I've updated the embedder string. Sorry for the delay with the response, but I wanted to test compiling with both 17.13 and 17.12 (on my other machine), and it works on both.

@marco-ippolito marco-ippolito changed the title win,build: Fix MSVS v17.14 compilation issue on v22 [22.x] win,build: Fix MSVS v17.14 compilation issue on v22 Jul 2, 2025
@marco-ippolito marco-ippolito added the request-ci Add this label to start a Jenkins CI on a PR. label Jul 2, 2025
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jul 2, 2025
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@marco-ippolito
Copy link
Member

marco-ippolito commented Jul 3, 2025

Can you rebase please? EDIT: nevermind, the CI can rebase on its own. We included #58799 on v22.x-staging so CI should be green

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

marco-ippolito pushed a commit that referenced this pull request Jul 3, 2025
Fixes: #58801
PR-URL: #58902
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Marco Ippolito <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
@marco-ippolito
Copy link
Member

Landed in d649e9a

RafaelGSS pushed a commit that referenced this pull request Jul 15, 2025
Fixes: #58801
PR-URL: #58902
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Marco Ippolito <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-ci PRs that need a full CI run. v8 engine Issues and PRs related to the V8 dependency. v22.x Issues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants