-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
Migrate crate-local /gen
directories to OUT_DIR
#687
Conversation
API docs are being generated and will be shortly available at: https://godot-rust.github.io/docs/gdext/pr-687 |
Seems fine on VSCode (for Linux) using Rust-Analyzer extension (v0.4.1943) |
7d166a9
to
e2711ab
Compare
VSCodium 1.87.2 on Linux (Flatpak version). Works out of the box. |
Works on Linux, VSCode + RustAnalyzer. Also tested whole build process and godot export on CI in |
9d7de11
to
6d6c15c
Compare
Tested on VSCode 1.89 (windows) with Rust Analyzer v0.3.1950, and there were no issues. I would also like to note that I can confirm that this resolves some rust analyzer panic/warnings when compared with the master branch. |
6d6c15c
to
274dd2b
Compare
Remnant from times where the header regularly had breaking changes. Since Godot 4.1, changes should generally be backwards compatible. Some patching still happens in Rust code, with direct String::replace() calls.
274dd2b
to
977f925
Compare
Bringing this to |
Please help test this pull request on different IDEs. In the past, we experienced problems with static analysis and symbol completion when using
OUT_DIR
.To try this PR, you can run
cargo clean
, then replace yourgodot
entry in Cargo.toml with this:Jetbrains
On Jetbrains IDEs, it may be necessary to run Cargo refresh:
Feedback
I'd appreciate if you could then respond here quickly with your IDE, its version and if things work (out of the box, or if a manual step like Cargo refresh is needed).
Closes #506.