`rust_libretro_sys::retro_log_level` is not FFI-safe about rust-libretro HOT 3 OPEN

At the moment bindgen is configured to emit non-exhaustive Rust enums because at the time I thought those are the most ergonomic version, but didn’t know all the consequences yet. :(
I started some work in the namespaced-sys branch to generate “constified enum modules” instead (and also offer easier to handle aliases in a module tree).

But instead of defining this log function you are supposed to use the RETRO_ENVIRONMENT_GET_LOG_INTERFACE environment callback to get the log interface from the frontend. :)

The abstraction crate provides a function to fetch said interface.
At the moment it uses std-types, but the important bits should be available in core.
You can find examples of how it is used here and here.

from rust-libretro.

But instead of defining this log function you are supposed to use the RETRO_ENVIRONMENT_GET_LOG_INTERFACE environment callback to get the log interface from the frontend. :)

I’m implementing the frontend :)

from rust-libretro.

Oh! Darn. That is a problem then. :s
You're only using the sys-crate, right?
In that case you should be able to patch the enum types in the build.rs without breaking lots of dependent code.
Could you try disabling the non-exhaustive flag, I think that's the only bit making them non-FFI-safe?
At the least this tells me that the refactoring / rewrite in the namespaced-sys branch is worth polishing.

from rust-libretro.