On Thu, Nov 17, 2022 at 11:55 AM Viresh Kumar viresh.kumar@linaro.org wrote:
On 17-11-22, 11:48, Bartosz Golaszewski wrote:
Let me propose a different solution. When preparing release tarballs with autotools, certain files are generated automatically that go into the tarball but are never part of the repository. This way developers don't have to deal with the automatically generated files polluting the repo while end-users get a tarball with less dependencies and reproducible results.
It's called the dist-local hook in automake.
Does it sound like something we could use here?
These auto-generated bindings are used only by the code present in bindings/rust/libgpiod/src/, and are never visible to end user code.
The end user will use the new interface provided by the libgpiod Rust bindings instead and that works over the web and will be picked from libgpiod's git tree or crates.io (later).
Not sure how the tarball solution will work here.
So it already only impacts developers exclusively and not users who'd for example want to install libgpiod from crates.io? If so then I don't really see a reason to keep those files in the repo really.
I'm not familiar with rust-vmm containers but the fact that bindgen support is missing or causes problems sounds like a problem with rust-vmm and not users of bindgen, right?
Bart