4 ms·
It also uses ramdisk on WSL or for those who use hard-drives for builds. Also great question about using nightly, we're using a shared-generics flag that requi
by XtremeDevX 4y ago
It also uses ramdisk on WSL or for those who use hard-drives for builds.
Also great question about using nightly, we're using a shared-generics flag that requires nightly (and speeds up build times).
We're working on making this more configurable to enable / disable what features you want.
- vladvasiliu 4y ago> It also uses ramdisk on WSL or for those who use hard-drives for builds. Yeah, I skipped over this, considering that most people doing rust dev will likely have some kind of SSD. I didn't look into how you went about doing this, but one thing that I'd like is to be able to move the target/ directory on a ram disk, or, generally, out of the source root [0]. If Fleet were able to do this transparently, it would be really great. --- [0] I know it's possible to define an external directory, but it applies to all projects, and it's not what I want, because shared crates would go overwrite each other.
- XtremeDevX 4y agoThis is exactly what we do, move the target/ directory on a ramdisk.
- VarunPotti 4y agoYep we also create a unique id for each project so that you can run 2 different rust apps during the same session, or else 1 rust projects build files would be mixed with the others how we go about this is we create a directory /dev/shm/<uuid> and symlinking this created directory into the rust projects target dir
- vladvasiliu 4y agoDo you think this could be somehow integrated with Cargo to be run with `cargo build`? The reason I'm asking is that I use the IntelliJ plugin for Rust dev which is kind of clunky and only understands a few commands as being "build", so it doesn't show the build window.