-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
src: remove util-inl.h include in node.h #27804
Conversation
`node.h` may only include public APIs, which `util-inl.h` is not. There does not seem to be any reason for including it, so remove it, because otherwise native addon compilation is broken due to us not shipping the `util-inl.h` header. Refs: nodejs#27631 Fixes: nodejs#27803
Please 👍 this comment to approve fast-tracking. |
How is it that CITGM couldn't catch this? |
@addaleax I'll try to put together a patch release tomorrow. |
@targos I think CITGM uses |
@addaleax could we for example, from citgm, copy the public headers to a temporary directory and point |
@targos Yeah, I assume there is some way to make something like that work… |
Landed in 47c5c3d |
`node.h` may only include public APIs, which `util-inl.h` is not. There does not seem to be any reason for including it, so remove it, because otherwise native addon compilation is broken due to us not shipping the `util-inl.h` header. Refs: #27631 Fixes: #27803 PR-URL: #27804 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Thinking about this further: would it maybe be possible to do something like that directly in each CI run instead of in our CITGM runs? |
Yes, it's possible. There was #12231 which stalled. |
It would be good to get #12231 going again. I added the broken includes because some test/cctest code was failing to build, code that included only (I thought at the time) "node.h", leading me to the wrong conclusion that those headers were expected as part of the node API. Building addon tests like actual addons would be very helpful. @targos Sorry for the trouble, and thanks for doing a fixup release. |
`node.h` may only include public APIs, which `util-inl.h` is not. There does not seem to be any reason for including it, so remove it, because otherwise native addon compilation is broken due to us not shipping the `util-inl.h` header. Refs: #27631 Fixes: #27803 PR-URL: #27804 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Notable changes * deps: * Fix handling of +0/-0 when constant field tracking is enabled (Michaël Zasso) nodejs#27792 * Fix `os.freemem()` and `os.totalmem` correctness (cjihrig) nodejs#27718 * src: * Fix v12.3.0 regression that prevents native addons from compiling nodejs#27804 PR-URL: nodejs#27814
node.h
may only include public APIs, whichutil-inl.h
is not.There does not seem to be any reason for including it, so remove it,
because otherwise native addon compilation is broken due to us not
shipping the
util-inl.h
header.Refs: #27631
Fixes: #27803
@BridgeAR It would be awesome if you could push out 12.3.1 with that soon, it completely breaks non-N-API addon compilation.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes