Fix dyld issue on macOS

[lrettig]

Fixes #6
Replaces #7

@fasmat this clears up the issue for me. Could you give it a shot?

[lrettig]

Assuming this works we should do the same in smcli

[fasmat]

This does fix make test but imo it doesn't fix the underlying issue.

rpath is set incorrectly in spacemesh-sdk - it sets the lookup path for libed25519_bip32 to /Users/aviv/actions-runner/_work/spacemesh-sdk/spacemesh-sdk/target/aarch64-apple-darwin/release/deps/.

Imo instead of overwriting the path in smkeys and smcli (and every other user of the library) by setting DYLD_LIBRARY_PATH we could set the right rpath in the library itself.

Since we statically link the finished binary I'm OK with this change, but if it would be dynamically linked the application couldn't be started without setting the DYLD_LIBRARY_PATH explicitly which I think is prevented by System Integrity Protection on most systems?

[fasmat]

See also https://blog.krzyzanowskim.com/2018/12/05/rpath-what/

[lrettig]

Imo instead of overwriting the path in smkeys and smcli (and every other user of the library) by setting DYLD_LIBRARY_PATH we could set the right rpath in the library itself.

See comment here: spacemeshos/spacemesh-sdk#5 (comment)

Basically, I don't think this is possible because we don't know the "right" rpath at build time. It's relative to the location of the dylib on this side when we run go build/test/....

[fasmat]

The change did the trick, rpath is not pointing to /Users/aviv/actions-runner/_work/spacemesh-sdk/spacemesh-sdk/target/aarch64-apple-darwin/release/deps/ any more and can now be set using CGO_LDFLAGS instead of DYLD_LIBRARY_PATH.

See my comment here: spacemeshos/spacemesh-sdk#5 (comment)

[fasmat]

Thanks @lrettig! ❤️