Open blopker opened 3 months ago
Hi! Thanks for opening your first issue here! :smile:
I should add that making rust_input: crate::api,caesium
errors with:
ror: package ID specification `caesium` did not match any packages
Did you mean `libcaesium`?
When trying to generate the bindings.
It has a [lib] section in the Cargo file that has a name declared, caesium, which seems to cause issues.
I think so, frb does not yet understand this field.
I'm not sure if this is a bug or feature request.
So yes it looks like a feature request
I guess it is not hard to fix it. Rough idea:
cargo_metadata
to get various info. then we can read that "name" field and know that rename thing.Feel free to PR for this! Alternatively, I may work on it in the next batch.
Great! I thought I might just be holding it wrong, but good to know it's unimplemented. My workaround is just to make a small Rust wrapper, which was easy enough.
I'm new to Rust, but I may end up trying to do it.
Anyway, thanks for this amazing project! It's been wonderful to work with.
You are welcome and looking forward to the PR! The wrapper looks reasonable since the API looks small.
Describe the bug
I'm not sure if this is a bug or feature request. I'm trying to auto generate bindings for the crate here: https://github.com/Lymphatus/libcaesium. It has a [lib] section in the Cargo file that has a
name
declared,caesium
, which seems to cause issues.My
flutter_rust_bridge.yaml
:This is able to generate the bindings, but they won't compile because the bindings try to import with
libcaesium
, when it needs to usecaesium
.I get a lot of errors similar to:
Thank you!
Steps to reproduce
libcaesium = { git = "https://github.com/Lymphatus/libcaesium.git", tag = "0.15.5" }
in Cargo.tomllibcaesium
to flutter_rust_bridge.yamlrust_input
flutter_rust_bridge_codegen generate
Logs
Expected behavior
No response
Generated binding code
No response
OS
MacOS
Version of
flutter_rust_bridge_codegen
2.0.0
Flutter info
Version of
clang++
No response
Additional context
No response