Crystal: Hardcoded path to libyaml-0.2.dylib in embedded/bin/shards

[nehaljwani]

crystal-0.24.2-1 release binary for macOS has a hardcoded path to libyaml-0.2.dylib:

(base) ➜  1524496023 otool -L /private/tmp/scratch.nwani/1524496023/crystal-0.24.2-1/embedded/bin/shards
/private/tmp/scratch.nwani/1524496023/crystal-0.24.2-1/embedded/bin/shards:
    /usr/local/opt/libyaml/lib/libyaml-0.2.dylib (compatibility version 3.0.0, current version 3.5.0)
    /usr/lib/libpcre.0.dylib (compatibility version 1.0.0, current version 1.1.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.60.2)
    /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)

To make it work, I had to tweak the binary with install_name_tool

[asterite]

Is that with homebrew? If not, can't you use homebrew?

[RX14]

looks like a packaging error, was crystal installed using homebrew or by downloading from the website?

[nehaljwani]

I do not use homebrew, so I downloaded the release binary.

[asterite]

Please use homebrew. I think nobody really tries the raw releases for mac as homebrew is so convenient...

[smorimoto]

Version managers such as asdf-crystal also have this problem. I think we can get path from CRYSTAL_LIBRARY_PATH. Is there a reason not to fix this?

[RX14]

@imbsky nobody's had the time to look into it unfortunately :(

[smorimoto]

Will the Crystal core team fix this?