added a troubleshooting section for macOS mojave

[ctrl-dlahr]

I ran into this issue recently trying out crystal and hoped to contribute!

crystal-7209

[straight-shoota]

Other relevant issue: crystal-lang/crystal#6875

[RX14]

Can't someone who uses homebrew just work out a solution to make homebrew package crystal properly? If it doesn't work out the box, it's a packaging problem, not crystal's problem.

[proyb6]

I concur, it’s a HomeBrew’s issue that devs have to googling manually for more than one way and work differently on different terminals. Could not recommend adding this advice on Crystal book.

[ctrl-dlahr]

@RX14 The Crystal Playground will not work on macOS Mojave without this troubleshooting step. I, as someone new to crystal thought it was really frustrating to figure out and considered not bothering since it was not an easy search. I was just casually checking it out which I think is common.

In my opinion if it is a problem that occurs for all or most X users you should add it to the troubleshooting guide to make the Crystal experience better for those users.

Crystal now installs pkg-config by default, but it doesn't expose that to OpenSSL installation and thus the crystal playground will always be broken until it is linked for macOS Mojave users.

Up to you guys :) appreciate your taking the time to review the pull request

[proyb6]

@codingdracula I checked yesterday pkg-config wasn’t installed by default

[ctrl-dlahr]

@proyb6 apologies, everyone should ignore the last part of my post. I didn't realize it was still open

[straight-shoota]

@codingdracula Thank you! Your contribution is very welcome. I think we should definitely merge this as a service to Crystal users in MacOS. Unless there is a way to avoid this problem altogether as @RX14 asked. That would be even better, if no troubleshooting was required in the first place.

[RX14]

In the short term we should merge this PR, but only after we've bought up this issue with homebrew, or the issue will end up being neglected.

[gregors]

@dustinlahr thanks for helping me solve my problem

[straight-shoota]

@dustinlahr Could you apply the suggestions from @bcardiff ?

[dkniffin]

Not sure if it belongs as part of this PR or another one, but this page on the website needs to be updated as well: https://luckyframework.org/guides/installing/

Right now it says:

If you are on macOS High Sierra ...

but I think Mojave needs to be listed there as well

[ctrl-dlahr]

added requested changes @bcardiff. Not sure if there is anything else I need to do. If there is let me know :)!

[bcardiff]

Thanks @dustinlahr

[RX14]

Has anyone been working on fixing this packaging issue? I'd do it myself if I had a mac.

[bcardiff]

@RX14 what could be changed to delay the issue is to avoid the dependency of ssl with the playground agent. Using pipes or sockets will be enough.

Other than that, when compiling an http server eventually the user will need some ssl and pkg-config configured accordingly.

[rdp]

Something doesn't feel quite right. Crystal is installed via a package manager. Then it subsequently cannot use the SSL dependency that was pulled in by the same package manager. At worst crystal should have a warning message in its brew package (at install time) but this should probably "just work" ... sadly it appears the instruction page is a bit outdated (you don't need to install openssl anymore, manually, and the path is now /usr/local/opt/openssl@1.1 FWIW)

[bcardiff]

I agree, eventually crystal via brew might have a wrapper script that will set up accordings paths to link directly to OpenSSL in brew probably.