-
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
Don't include common.gypi from node source tree #1118
Comments
I would support this change. I got burned by the fact that |
Node.js 10's which may expose anyone using older compilers to compile addons. |
Yep, but that flows on down from V8. We'd still carry that change with a separate common.gypi. |
still planning on making this happen @bnoordhuis? I fear this is just going to linger as a perpetually open issue unless you make it happen, I suspect there's too many dragons for most mortals to want to attempt this |
@rvagg It's one of those projects that I do want to get around to someday but I don't know when. If you want to close it, that's fine by me. Good job on the cleanup action, by the way. :-) |
I think I got throttled along the way with my cleanup, I stopped being able to close issues, a red error box from GitHub as if I was blocked. Seems to be working again now. I don't mind this being left open if it's genuinely a TODO, your call. I'm just aiming to get rid of the clutter so this starts being manageable again. |
node-gyp includes
$nodedir/common.gypi
when creating build files for an add-on.Per nodejs/CTC#62 (comment), that probably isn't future-proof and it's a bad idea in general: it makes add-ons pick up compiler and linker settings that aren't intended for them and may be actively harmful. People have filed bug reports about it.
Plan of action:
common.gypi
intoaddon.gypi
.The text was updated successfully, but these errors were encountered: