Add check for OpenSSL on OS X before starting the language service

[daviwil]

The extension should check for the existence of OpenSSL on OS X before starting the language service. If it cannot be found, the user should be directed to the documentation which guides them through the OpenSSL installation.

One way to check for existence could be to test for the existence of /usr/local/opt/openssl

[MarlonRodriguez]

That check on the path only works if you are using homebrew. For MacPorts:

ln -s /opt/local/lib/libcrypto.1.0.0.dylib /usr/local/lib/
ln -s /opt/local/lib/libssl.1.0.0.dylib /usr/local/lib/

fixes it.

[daviwil]

Thanks a lot @MarlonRodriguez! I'll include your fix in the troubleshooting notes.

[adbertram]

It'd be nice if a link to some instructions on how to resolve this were added to the notification as well.

[daviwil]

That's what the "Show Documentation" button on the notification does, did it not show up for you?

[adbertram]

I'm blind. Thanks but I had originally installed it. It wasn't until I
updated again to this latest version that I saw that popup and Intellisense
isn't working.
When I run brew install openssl I get:

openssl-1.0.2h_1 already installed

On Sun, Sep 4, 2016 at 5:38 PM, David Wilson [email protected]
wrote:

That's what the "Show Documentation" button on the notification does, did
it not show up for you?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#264 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEG3-h7aVQiG6so4vrUypmzoAf-PU98tks5qm0hSgaJpZM4JtZk_
.

[daviwil]

Interesting, @RamblingCookieMonster mentioned the same thing to me yesterday. If you follow the steps in the documentation page about creating symbolic links it should fix the problem for you.

Quick question before you do that though: was IntelliSense working for you without a problem on OS X before the latest update? Maybe I'm checking the incorrect path for Brew's install of OpenSSL.

[RamblingCookieMonster]

@adbertram try this (probably a way to script this out, but, a bit busy, sorry!):

• brew info openssl
• Pick out the path to the latest, e.g. /usr/local/Cellar/openssl/1.0.2h_1 - find /usr/local/Cellar -name libssl.1.0.0.dylib might also work.
• Create links mentioned above.

Example:

ln -s /usr/local/Cellar/openssl/1.0.2h_1/lib/libcrypto.1.0.0.dylib /usr/local/lib/
ln -s /usr/local/Cellar/openssl/1.0.2h_1/lib/libssl.1.0.0.dylib /usr/local/lib/

Doesn't seem sustainable though, cleanups happen, and this links to a version-specific (i.e. likely temporal) file.

Cheers!

[adbertram]

Thanks @RamblingCookieMonster! That did it.

[adbertram]

@daviwil Yes. This was working fine before I updated.

[daviwil]

Damn, so apparently my path check gave a false negative for Homebrew installs... I'll need to look into that.

[daviwil]

Tracking the false negative problem here: #286. Thanks Adam!