-
Notifications
You must be signed in to change notification settings - Fork 135
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
Simplify binding.gyp #149
base: master
Are you sure you want to change the base?
Simplify binding.gyp #149
Conversation
On Windows from Node 6.3.0 onwards the OpenSSL symbols are exported so we don't need to look for them. Further, OpenSSL 1.1.0 onwards has renamed the libraries so not relying on a given name means we don't have to detect which version is installed.
I'm looking for a new maintainer: https://github.com/quartzjer/ursa#maintainer-needed |
I guess the first question is what are the alternatives if ursa went away? |
I have had no success install ursa on Node 6.10.0 or 7.6.0 on Windows 10. When you said 6.3.0 did you mean that version or earlier? |
@davedoesdev it's been awhile since you worked on this, how do you feel about it?
|
I've moved away from |
On Windows, Node 6.3.0 exports the OpenSSL symbols which means we don't have to look for them. It also means we don't have hassle when OpenSSL change their library names as happened in 1.1.0.
Note if this change goes in then on Windows ursa would require Node 6.3.0 or above.
I'm not sure whether this would be an acceptable price to pay for more reliable Windows support going forward.