liburing-ffi headers

im linking to liburing-ffi.a
you says that

Users wishing to consume liburing purely as a binary dependency
should link against liburing-ffi. It contains definitions for every 'static
inline' function.

im using rustbindgen to generate rust definition of c headers
but rustbindgen cannot handle inline functions
i need liburing-ffi.h instead of liburing.h

changed
rustbindgen can handle static inline

@axboe there's two libraries "liburing.a" and "liburing-ffi.a",but
there's only one header. It makes no sense

@cmazakas

is ffi varient just -fno-inline-functions
What's the difference

[ammarfaizi2]

Languages and applications that can't use 'static inline' functions in
liburing.h should use the FFI variants.

If you can use the header, then there is no point in using FFI.

The FFI version is supposed to be used by programming languages that
can't use the liburing.h header. IOW, other than the C/C++ language.

how do i get metadata without header

I don't even know the signature of the function because there is no header
In other words, how do I create function signatures in other languages ​​without C header

[ammarfaizi2]

I don't even know the signature of the function because there is no header

The signature doesn't change; still the same as the non-FFI version.

What programming language are you working on?

[ammarfaizi2]

In other words, how do I create function signatures in other languages ​​without C header

Use the same signature as the non-FFI version.

im using rustbindgen to generate rust definition of c headers
but rustbindgen cannot handle inline functions

Does it mean that if liburing-ffi.h exists, just delete all static inline and function body?

[ammarfaizi2]

Does it mean that if liburing-ffi.h exists, just delete all static inline and function body?

Yes, exactly.

rustbindgen is an automated tool to generate rust bindings from c language headers, I don't like manual bindings because manual is fragile and complicated

I mean liburing-ffi.h is needed because the existing C header files are not suitable for rustbindgen or similar automation tools, and this may make things less complicated

[ammarfaizi2]

I don't know about rustbindgen, but from a quick google, I found this:

rust-lang/rust-bindgen#2335

Does that solve your problem?

I tried, it didn't help, it just made things more complicated

Link time optimization should be able to ignore static inline