[Update] A solution has been found: https://github.com/robhawkes/node-extension/issues/1
I'm embedding Node within a browser extension and don't want the user to manually install openssl or even know what it is, I'd rather it was bundled into the Node build or statically linked to files held within the browser extension.
I already know how to disable openssl completely in Node and that solution works, however I'd like to have openssl enabled incase my users require it at some point.
I'm also aware of the --openssl-includes
and --openssl-libpath
./configure
flags, however they didn't seem to do what I wanted when I pointed them to a directory containing a static build of libssl and crypto – the build failed because it couldn't find the "SSL_library_init" function.
Any ideas how I can do this? If it help, I'm happy with a solution just for OS X for now. I can work out the rest later.
I appreciate the help.