rust-lang / rust-lang/rust-bindgen
Check and log libclang version in library usage, not just bin
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
I ran into some trouble testing build-time bindgen in Stylo today because I didn't realize I needed to set CLANG_PATH appropriately, and was getting nonsensical backtraces along with errors about undeclared identifiers in header files. I think it'd be good to add a min_version: Option<clang_sys::CXVersion> to BindgenOptions, which Bindings::generate can then check against the returned version from clang_sys::support::Clang::find(), complaining if the version found isn't new enough, with a friendly error message. Then Stylo can provide the appropriate version and everybody can walk away happy.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing BindgenOptions and Bindings::generate, then inspect how clang_sys::support::Clang::find() reports the discovered version. Verify how Stylo could provide a minimum version and define the friendly failure behavior when the found libclang version is too old.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100