-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should this use Rust ABI dylib
or the C/C++ ABI cdylib
#4
Comments
What change is needed to switch to |
It just requires changing Hopefully @dasmoth or Andy have some ideas what this decision entails. |
Tagging @andy-thomason so he sees this issue. |
It seems that cdylib is intended for building C API extensions for other things that dylib is for extending Rust frameworks and presumably allows rust functions I would definitely go for cdylib as the C ABI has remained invariant for decades |
Sounds good, I'll switch to cdylib. |
This is done now. |
While diagnosing my initial build issues on windows, see #2 , I found this thread describing the difference between
cdylib
anddylib
. Turned out, it wasn't an issue for me to usedylib
, but this might be a problem down the line. Also, r-rust/hellorust usescdylib
.This is specifically concerning the generated
Cargo.toml
file in thesource.R
file.The text was updated successfully, but these errors were encountered: