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
fix: generate valid config.gypi #31404
Conversation
🥇 |
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.
Looks OK to me.
Merging as CI failure is known flake unrelated to PR change. |
Release Notes Persisted
|
I was unable to backport this PR to "14-x-y" cleanly; |
I was unable to backport this PR to "15-x-y" cleanly; |
I was unable to backport this PR to "16-x-y" cleanly; |
Description of Change
Currently Electron generates a malformed
config.gypi
file in Node headers, which is fine since it is actually ignored by node-gyp when building modules.However with nodejs/node-gyp#2497, the
config.gypi
file in Node headers is going to be respected, and with it we will finally be able to get rid of our patches on Node'scommon.gypi
file. And to make Electron's Node headers work correctly with node-gyp, we must generated a validconfig.gypi
file.Release Notes
Notes: Generate valid config.gypi file in Node.js headers.