Closed amw-zero closed 3 years ago
I have a PR for the removal of no-link
from the example app code's Cargo.toml
here: https://github.com/danielpclark/rutie/pull/136
cc @danielpclark
Thanks for tagging me in this.
I’ve opened issues before where the maintainer did not get a notification automatically. Hopefully that didn’t come off as pushy, and if it did I apologize.
Not pushy at all. I don't get notifications unless I'm tagged or following something. It was, and is, a sincere thanks.
@amw-zero Just out of curiosity what OS are you using?
This happened to me on MacOS version 10.15.7.
@amw-zero Can you try it with Rutie v0.8.2 ? The build script previously had issues if rutie
is included with a relative path. I don't know if that's how you were including it.
I have made it so that the no-link option is not on by default as I believe it was causing more problems for users than it was helping... but the option is still there. If this is no longer an issue please feel free to close the issue.
Following the example code in the README for calling Rust from Ruby led to the following error for me:
MacOS version 10.15.7 Rutie version 0.8.1 Ruby version 2.7.2 (compiled with
--enable-shared
). rustc version 1.48.0This error means that the Rust --> Ruby bindings have not linked (i.e. here) the Ruby C library.
I noticed that the example app in the repo does not specify the no-link cargo feature, and removing that feature from my example app allowed
rutie
to compile.