-
Notifications
You must be signed in to change notification settings - Fork 301
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
Improve build.rs
configuration documentations
#1742
Labels
bug
Something isn't working
Comments
Totally agree! Seems that #1696 does not fully update everything. Thus maybe:
|
fzyzcjy
changed the title
in v2, build.rs configuration is not clear
Improve Feb 8, 2024
build.rs
configuration documentations
Ups, did not see that PR! |
Take your time! (I have edited my comment above) |
5 tasks
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
When trying to implement a build.rs, so changes in the rust code trigger code generation, I stumbled over the following issues:
Another build.rs can be found here, its cargo.toml points to the local frb repository (as CI should take the latest unpublished code).
However, it is not documented what needs to be imported when using the published code.
Steps to reproduce
Works, if the missing peaces are figured ;)
Logs
Expected behavior
No response
Generated binding code
No response
OS
No response
Version of
flutter_rust_bridge_codegen
No response
Flutter info
No response
Version of
clang++
No response
Additional context
I will create a small PR describing the setup better and fixing the link :)
The text was updated successfully, but these errors were encountered: