Skip to content

Over enforced naming in shared library name? #3209

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

Open
All8Up opened this issue May 21, 2025 · 0 comments
Open

Over enforced naming in shared library name? #3209

All8Up opened this issue May 21, 2025 · 0 comments

Comments

@All8Up
Copy link

All8Up commented May 21, 2025

While using bindgen against a library with a name such as '-1.0.0', bindgen generates " is not a valid Ident". This seems overly restrictive given that many libraries use such conventions. Renaming to '_1.0.0' also produces the same issue as '.' is not allowed in the name. Bindgen seems to be forcing a validation of the name against Rust "Ident" which is severely limiting when used against common library naming practices. I would expect that the name of the shared library should allow arbitrary conventions without this limit as the generated code does not seem to reference the name in any notable manner, at least with the settings I'm using.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant