rust-lang / rust-lang/rust-bindgen
[feature-request] mapping headers to modules
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
I have a wrapper.h that wraps a C library called foo and looks like this:
#include <foo/a.h>
#include <foo/b.h>
Currently bindgen dumps everything into the top of my crate. I'd like the code generated by bindgen to instead produce two modules pub mod a; and pub mod b; and expose that instead.
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 with the wrapper.h example and trace how bindgen currently handles the included foo/a.h and foo/b.h headers. Identify the entry point responsible for emitting declarations and determine how separate public modules should be represented. Done means the generated bindings expose a and b as distinct public modules rather than placing everything at the crate root.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100