2

Lets say there is a libfoo C library with matching headers. Documentation of bindgen suggests libfoo-sys crate should build dynamically on the client side, using their installed header versions. The accompanying libfoo crate is done manually by a developer and contains wrappers for a specific supported version. There might be functionality in the crate that is missing in older C versions, also the crate might be missing functionality a newer C version has. If C-libfoo uses semantic versioning the matching crate can just adopt the version of the C library, but is there an official way to communicate which version of C-libfoo a certain libfoo crate does match to if the original C library uses some proprietary versioning scheme?

Improve this question
1
  • 2
    There are crates that add the C version as build metadata to their own crate version. Like 1.2.3+7.8.9 as seen in libgit2-sys, rdkafka-sys, or curl-sys. Commented Aug 22 at 14:53
Related questions
1
Force jlrs to use newer bindgen?
16
Does semantic versioning apply to source or binary compatibility?
0
Cargo doesn't build winit with nokhwa bc of web-sys dependency
Load 6 more related questions Show fewer related questions

0

Reset to default

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.