Skip to content
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

VSCode, Rust-analyzer recompiling issue in Bevy 0.13.2 #1158

Open
SnappierSoap318 opened this issue Apr 29, 2024 · 1 comment
Open

VSCode, Rust-analyzer recompiling issue in Bevy 0.13.2 #1158

SnappierSoap318 opened this issue Apr 29, 2024 · 1 comment
Labels
A-Book C-Correction A typo or factual issue in what we've written S-Needs-Investigation We need to figure out what's going wrong

Comments

@SnappierSoap318
Copy link

How can Bevy's documentation be improved?

In the Setup page, it is given that the new cargo config file should be located in <game>/.cargo/config.toml. I had a problem where the game would recompile every time i ran it,

My suggestion is to add an extra rust-analyzer setting flag to force it use the new config.toml file.

In settings.json add the "rust-analyzer.cargo.targetDir": true flag to force rust-analyzer.

@james7132
Copy link
Member

This might need to be moved to the website repo instead, since that's where the introduction/book is kept.

@alice-i-cecile alice-i-cecile changed the title VSCode, Rust-analyzer recompiling issue in 13.2 VSCode, Rust-analyzer recompiling issue in Bevy 0.13.2 May 13, 2024
@alice-i-cecile alice-i-cecile transferred this issue from bevyengine/bevy May 13, 2024
@alice-i-cecile alice-i-cecile added A-Book C-Correction A typo or factual issue in what we've written S-Needs-Investigation We need to figure out what's going wrong labels May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Book C-Correction A typo or factual issue in what we've written S-Needs-Investigation We need to figure out what's going wrong
Projects
None yet
Development

No branches or pull requests

3 participants