Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
zig
General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
-
llvm-project
The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Cross compiling with cargo has always been relatively simple; that's what you get by designing a default cross compiling toolchain. cargo cross also exists to make cross compilation and testing even simpler for most cases.
I am a noob and Rust is the first environment where I did cross compiling. I am also blown away by how easy and quick this works. However, with a new project it does not work anymore, because it involves a dynamic library (.so on Linux or .dll on Windows); specifically talking about libarchive with help of compress-tools.
Rust's approach is more inline with their philosophy of "taking as long as necessary to do it properly". (eg. linking with LLD is still a work in progress but it will improve LLD for everything LLD-based. rustc_codegen_gcc may not be as much of an independent implementation as gccrs, but the project is getting patches into libgccjit's AOT compilation API to improve it for everyone.)
Small correction: while zig's compiler-rt has many functions ported from LLVM's, it is a different codebase that has more capabilities and fewer limitations than LLVM's compiler-rt.
Small correction: while zig's compiler-rt has many functions ported from LLVM's, it is a different codebase that has more capabilities and fewer limitations than LLVM's compiler-rt.