-
-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile UniFFI interfaces defined in sibling libraries #2090
Comments
Unfortunately the generated python file name can only be inferred from |
Hey @messense, thanks for the response. I had a [bindings.python]
cdylib_name = "odict" and running Maturin it's still looking for |
Can you try change this to |
So I actually tried that, and I believe Rust complains if there are two crates that produce libraries with the same name. Away from my keyboard at the moment, but I can safely say it errored and failed to build when I tried that :/ |
@messense Any further suggestions? 🥺 |
Hey folks,
I'm currently trying to adopt Maturin in my monorepo, which is attempting to use UniFFI to export FFI interfaces for Kotlin and Python from a shared Rust crate (
odict
). The core library is setup to use FFI, and upon compiling will produce a .py file in the target directory:However, because Maturin expects you to be building your UniFFI interface from the current project, it's looking for
pyodict.py
(the Python library/binding where I'm using Maturin).This file doesn't exist and causes an error:
I'd love it if Maturin would allow you to create wheels from shared FFIs like this, instead of forcing you to keep it all in a single project. I combed the docs but couldn't find a way to do this. Hopefully I'm not missing something.
The text was updated successfully, but these errors were encountered: