But can it generate bindings for multiple abi variants?
This would seem extremely complicated to automate.
It can understand preprocessor macros, and the FFI's CLinker class understands different platform ABIs. So I guess you could generate several different packages with variant ABIs, abstract over them and then use whichever one seems to be available.
Abstract over them meaning writing wrappers by hand?
The ABI stuff is taken care of at runtime.
What do you mean?
You only specify the function signatures and structs. The JVM then figures out how to put arguments and return values into registers/stack/whatever at runtime, depending on which OS and CPU it's running on. That's what the `CLinker` class is responsible for. It's like regular dynamic linking, but taken a bit further.
The problem is structs and function signatures of standard APIs can have differences for each os/version combination.
Then you have to take care of making sure you call the right thing. But I suppose this doesn't happen very often because OS APIs usually maintain backwards compatibility. Also a well-designed API would take complex structs by pointer, thus allowing the addition of fields at the end without breaking the ABI.