cargo-raze
sccache
Our great sponsors
cargo-raze | sccache | |
---|---|---|
6 | 70 | |
475 | 5,347 | |
0.6% | 3.0% | |
1.7 | 9.4 | |
23 days ago | 1 day ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cargo-raze
-
NixOS: Declarative Builds and Deployments
The same reason Bazel builds avoid using Cargo when building Rust software, so I'll describe why Bazel would do this:
- Bazel wants to cache remote resources, like each respective crate's source files.
- Bazel then wants to build each crate in a sandbox, and cache the build artifacts
This is an established practice, and Nix wants to drive the build for the same reasons.
See:
- https://github.com/bazelbuild/rules_rust
- https://github.com/google/cargo-raze
- Rust Is Portable
-
Regarding what happened to P0447: Why?
I can make much more sense of C++ code to ensure that two build systems produce the same effect than I can parse and learn two completely unconnected programming languages deeply enough to do the same. I can unit-test core routines. I can as easily extract core logic into shared (configuration) files etc. The benefit of a standard is not to discourage alternatives but rather to agree on definitive semantics and shared and common needs (that is: in this case needs for interfaces to the compiler/linker). The implementation and general availabilty is just one of the by-product. The ability to do introspection in common terms is maybe the most consequential other product, and this is critical for 'transpiling' to other build systems and writing automated adapters such as the one that bazel is recommend for cargo's dependency management.
-
What is your favorite programming language?
Cargo is not that tightly coupled with Rust. You can absolutely use bare rustc, and in fact people do that with other build systems like Bazel.
-
Six Years of Rust
Interesting, aren't the community-driven crates for these areas satisfactory enough? There's PROST and tonic, and quite well-used. I don't know about Bazel though, but I found this. Feel free to correct me on this subject, I admit I don't know that much about it.
-
Integrating Rust Into the Android Open Source Project | Google Security Blog
There is a project to generate Bazel BUILD files from Cargo.toml.
sccache
-
Mozilla sccache: cache with cloud storage
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.
- Welcome to Apache OpenDAL
-
Target file are very huge and running out of storage on mac.
If you have lots of shared dependencies, maybe try sccache?
-
S3 Express Is All You Need
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
- sccache
-
Serde has started shipping precompiled binaries with no way to opt out
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.
-
Cache dependencies across crates
Checkout https://github.com/mozilla/sccache
-
Distcc: A fast, free distributed C/C++ compiler
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)
-
How to fix Rust Coding LARGE files????
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.
-
On the verge of giving up learning Haskell because of the terrible tooling.
That's definitely not my experience. Never had any issue running Rust on Windows. You just download and run rustup-init.exe, then updating is simply a matter of rustup update. Documentation generation is built in (cargo doc) and just a case of annotating code with triple-/ markdown comments and then running that command. sccache works fine for me (just need to set RUSTC_WRAPPER=/path/to/sccache). And the error messages from rustc are by far the best of any compiler I've used. Not sure how they're unhelpful, they tend to explain step-by-step what the problem is and how to fix it.
What are some alternatives?
prost - PROST! a Protocol Buffers implementation for the Rust Language
ccache - ccache – a fast compiler cache
tonic - A native gRPC client & server implementation with async/await support.
cargo-chef - A cargo-subcommand to speed up Rust Docker builds using Docker layer caching.
prost - PROST! a Protocol Buffers implementation for the Rust Language
rust-cache - A GitHub Action that implements smart caching for rust/cargo projects
dmd - dmd D Programming Language compiler
cache - Cache dependencies and build outputs in GitHub Actions
Metals - Scala language server with rich IDE features 🚀
icecream - Distributed compiler with a central scheduler to share build load
pyroscope-rs - Pyroscope Profiler for Rust. Profile your Rust applications.
mold - Mold: A Modern Linker 🦠