We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For shared modules on macOS, the library suffix is often .so, but cargo will always create .dylib for cdylibs.
.so
.dylib
Is there a way for cargo-c to tell cargo what suffix to use for a shared library?
The text was updated successfully, but these errors were encountered:
I need to check if cargo has a mean to override that. That I recall is hardwired, but had been long since I looked that part.
Sorry, something went wrong.
See also rust-lang/cargo#1706 (comment)
No branches or pull requests
For shared modules on macOS, the library suffix is often
.so
, but cargo will always create.dylib
for cdylibs.Is there a way for cargo-c to tell cargo what suffix to use for a shared library?
The text was updated successfully, but these errors were encountered: