cargo-xwin
crates.io
cargo-xwin | crates.io | |
---|---|---|
6 | 662 | |
286 | 2,802 | |
7.3% | 1.2% | |
8.0 | 10.0 | |
13 days ago | 4 days ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | 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-xwin
-
[Review] Introducing cargo-xwin: A Solution for Cross-Compiling Rust on macOS to MSVC
Today, I am excited to introduce a real game-changer - the [cargo-xwin](https://github.com/rust-cross/cargo-xwin) crate! After countless trials and errors, cargo-xwin was the only one that truly met my needs.
-
Release Engineering Is Exhausting So Here's cargo-dist
I couldn't tell you the licensing implications but the cargo-zigbuild developer also made cargo-xwin: https://github.com/rust-cross/cargo-xwin
-
Crosscompiling from fedora to Windows
I thought you could already cross compile to -windows-msvc targets from Linux using cargo-xwin?
-
Cross-compilation in Rust
I've personally used cargo-zigbuild and cargo-xwin to distribute a GUI app built with iced.
-
cargo-xwinbuild v0.3.0 supports cross compile to Windows with CMake dependency
cargo-xwinbuild is a thin wrapper of xwin provides a Cargo subcommand xwinbuild to make cross compiling to Windows MSVC target just work.
-
Announcing cargo-xwinbuild: Cross compile Cargo project to Windows msvc target with ease
So I thought I can try to make another Cargo subcommand which integrates xwin and automates the boring stuffs for you, here comes cargo-xwinbuild: https://github.com/messense/cargo-xwinbuild
crates.io
-
Create a Custom GitHub Action in Rust
Rust has a rich ecosystem of frameworks and libraries that let you read, parse, and manipulate text files, interact with cloud services and databases, and perform any other job that your project's development workflow may require. And because of its strong typing and tight memory management, you are much less likely to write programs that behave unexpectedly in production.
-
Rust Keyword Extraction: Creating the YAKE! algorithm from scratch
All the code discussed in this article can be accessed through this repository. For integration with existing projects consider using keyword_extraction crate available on crates.io.
-
Migrating a JavaScript frontend to Leptos, a Rust framework
So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. Thereβs a good chance the crates you need are available in Rust's crates.io repository.
-
Learning Rust: A clean start
The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.
-
#2 Rust - Cargo Package Manager
Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.
-
Rust π¦ Installation + Hello World
Before proceeding, let's check https://crates.io/, the official Rust package registry.
-
Underestimating rust for my Project.
The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.
-
Top 10 Rusty Repositories for you to start your Open Source Journey
5. Crates.io
-
Project Structure Clarification Coming From Python - With Example
When using crates from eg. crates.io, and also things like std and core
-
Cargo has never frustrated me like npm or pip has. Does Cargo ever get frustrating? Does anyone ever find themselves in dependency hell?
Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.
What are some alternatives?
cargo-dist - π¦ shippable application packaging
docs.rs - crates.io documentation generator
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
plotters - A rust drawing library for high quality data plotting for both WASM and native, statically and realtimely π¦ ππ
xwin - A utility for downloading and packaging the Microsoft CRT headers and libraries, and Windows SDK headers and libraries needed for compiling and linking programs targeting Windows.
Cargo - The Rust package manager
cargo-zigbuild - Compile Cargo project with zig as linker
trunk - Build, bundle & ship your Rust WASM application to the web.
darling - Darwin/macOS emulation layer for Linux
gtk4-rs - Rust bindings of GTK 4
Rocket - A web framework for Rust.
embassy - Modern embedded framework, using Rust and async.