-
Notifications
You must be signed in to change notification settings - Fork 284
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
Building NodeJS with a shared v8 #3302
Comments
@fmoraes74 is this still an issue?
what would be your use case? if you have a compelling reason, feel free to raise an RFE in core. |
One main reason is that Node.js also liberally applies patches against V8 and is unlikely to build or link successfully against a precompiled, unpatched version of V8. |
It used to be possible a long time ago but was removed (nodejs/node#1331) due to issues with compatibility between different versions of V8 (which does not follow semantic versioning). |
I think if nodejs provide a libv8.so for some external project it is will good solution |
It seems there has been no activity on this issue for a while, and it is being closed in 30 days. If you believe this issue should remain open, please leave a comment. |
It seems there has been no activity on this issue for a while, and it is being closed. If you believe this issue should remain open, please leave a comment. |
It is possible to build node to use the embedded deps for v8 but built as a shared library? Seems like node always wants
v8
to be built as a static library but I want it to usev8
as shared library.The text was updated successfully, but these errors were encountered: