veloren VS sccache

I've never used it, but (from what I've seen) is a great tool for modeling Voxels.

Shameless plug: The format (and the tool) had been used with great success in Veloren, an Open Source Voxel MMORPG written in rust (https://www.veloren.net/). The artist team has made great assets for the game and landscapes for the release parties.

Your should check out the project, it is really cool.

(Disclaimer: I'm part of the mod team.)

There are instructions here

Someone from my uni already did it. Here it is

Veloren is a multiplayer voxel RPG written in Rust\ (132 comments)

Use icecream or sccache. sccache supports distributed builds.

https://github.com/mozilla/sccache/blob/main/docs/Distribute...

Worth noting that the first commit in sccache git repository was in 2014 (https://github.com/mozilla/sccache/commit/115016e0a83b290dc2...). So I suppose that what "happened" happened waay back.

If you have lots of shared dependencies, maybe try sccache?

I'm going to set up sccache [0] to use it tomorrow. We use MSVC, so EFS is off the cards.

[0] https://github.com/mozilla/sccache/blob/main/docs/S3.md

I think the primary benefit of pre-built procmacros will be for build servers which don't use a persistent cache (like sccache), since they have to compile all dependencies every time. But IMO improved support for persistent caches would be a better investment compared to adding support for pre-built procmacros.

Checkout https://github.com/mozilla/sccache

https://github.com/mozilla/sccache is another option which addresses the use cases of both icecream and ccache (and also supports Rust, and cloud storage of artifacts, if those are useful for you)

That being said a compilation cache, eg the de-facto standard for Rust: sccache (https://github.com/mozilla/sccache) will help to compile and store some of the build artifacts centralized - still for each crate version + build profile (RUSTFLAGS) combination.