dazel
cargo-raze
dazel | cargo-raze | |
---|---|---|
2 | 6 | |
159 | 474 | |
- | 0.0% | |
3.7 | 1.7 | |
6 months ago | about 1 month ago | |
Python | Rust | |
MIT License | 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.
dazel
- Rust Is Portable
-
Running container_push inside a container
My goal was to build a Bazel workspace that's not dependent on the system's OS, so I developed a docker container that should take care of it (There's a cool open source project, dazel, but I couldn't get it to work).
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.
What are some alternatives?
pyroscope-rs - Pyroscope Profiler for Rust. Profile your Rust applications.
prost - PROST! a Protocol Buffers implementation for the Rust Language
rules_closure - Closure rules for Bazel
tonic - A native gRPC client & server implementation with async/await support.
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
prost - PROST! a Protocol Buffers implementation for the Rust Language
pyzmq - PyZMQ: Python bindings for zeromq
dmd - dmd D Programming Language compiler
sixel-tmux - sixel-tmux is a fork of tmux, with just one goal: having the most reliable support of graphics
cosmopolitan - build-once run-anywhere c library
Metals - Scala language server with rich IDE features 🚀