Skip to content
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

[cffi] Allow generated shared library to have a name other than native.so #1919

Closed
timkpaine opened this issue Jan 21, 2024 · 2 comments · Fixed by #1918
Closed

[cffi] Allow generated shared library to have a name other than native.so #1919

timkpaine opened this issue Jan 21, 2024 · 2 comments · Fixed by #1918
Labels
bindings/cffi cffi bindings enhancement New feature or request

Comments

@timkpaine
Copy link
Contributor

When using the cffi backend, the generated shared library is always named native.so. It would be good if this:

  • was configureable or
  • matched the name of the library (e.g. my_extension would generated my_extension.so or libmy_extension.so)
@messense
Copy link
Member

When using the cffi backend, the generated shared library is always named native.so

Is there any real issues caused by the hard-coded name?

@messense messense added the bindings/cffi cffi bindings label Jan 22, 2024
@timkpaine
Copy link
Contributor Author

timkpaine commented Jan 22, 2024

@messense linking against multiple libraries generated in this fashion (which i plan on doing)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bindings/cffi cffi bindings enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants