Add section to "Working in WSL2" about natively compiling about bevy-cheatbook HOT 5 OPEN

I have been cross compiling for awhile and the startup time when launching for the first time after build does take a very long time. But launching for the second time for the same build is instantaneous. I have no clue why that is the case.

from bevy-cheatbook.

I experienced the same when I was cross compiling. I suspect it's windows caching the file in RAM which causes subsequent launches to be effectively instantaneous. Not very helpful when you're iterating quickly though lol.

from bevy-cheatbook.

How should Rust-Analyzer be configured?

I've setup a project-scoped .cargo/config.toml in WSL that has the config:

[build]
target-dir = "C:\\Users\\USER\\bevy_builds"

My WSL Rust-Analyzer just straight up create a directory in my project with the name 'C:\Users\USER\bevy_builds'

There's also this issue. I have my project directory that stays in C:\... and symlinked to my WSL which causes cargo config issue. Seems like I may need to restructure my stuff.

from bevy-cheatbook.

Your .cargo/config.toml that sets the build.target_dir needs to be on the windows side at C:\Users\NAME\.cargo\config.toml, not the WSL2 side.

Also, my setup assumes your project lives in WSL2's linux filesystem, not your windows filesystem. I'm not sure how it would behave with the setup you've described where your project lives in your windows filesystem with it symlinked to your WSL2 linux filesystem.

With my setup, rust-analyzer has needed no extra configuration from the norm. It does native linux builds for checking and stores that in my project dir in target/.

from bevy-cheatbook.

I've restructured my projects directory for a bit. Having 2 builds for both Windows and Linux will probably took a bit of space but worth the trade-off. Anyways this works beautifully. Thanks for the tutorial!

from bevy-cheatbook.