cygwin-rurban
xwin
| cygwin-rurban | xwin | |
|---|---|---|
| 1 | 5 | |
| 0 | 327 | |
| - | - | |
| 10.0 | 7.4 | |
| almost 5 years ago | about 1 month ago | |
| Diff | Rust | |
| - | 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.
cygwin-rurban
xwin
-
Because cross-compiling binaries for Windows is easier than building natively
There's tooling that mostly avoids this. https://github.com/Jake-Shadle/xwin
This is a utility that fixes a lot of the cross-compiling issues for windows by giving you a portable, unfucked naming, and not-massive SDK. It's the same SDK you get when you install MSVC but it's only a few hundred megs and the names are consistent even with all of Windows' fucked up tooling.
The only caveat is you need to provide your own compiler, in this case clang is often the best option.
-
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
This situation bugs me a lot, and I remembered a blog post about the xwin which makes cross compiling Windows binaries from Linux quite easy, but it requires a lot of manual setup. While using Docker containers make it easier, it's also slower.
-
Am I the only one who finds Rust to be centered around Linux? Any Windows devs want to share their experience with Rust?
I will do you one better. When I do windows development, I work within WSL and use the cross-compiler toolchain to generate windows binaries. I have found "Xwin" to be very useful for this: https://github.com/Jake-Shadle/xwin
-
Blog post: Cross compiling Rust Windows binaries from Linux
I've just pushed a 0.1.1 release that fixes this issue, unsure why the windows crate decided to use screaming case in their link names but I'm sure they're not the only ones.
What are some alternatives?
WSL - Issues found on WSL
cargo-deny - ❌ Cargo plugin for linting your dependencies 🦀
winget-cli - WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
llvm-mingw - An LLVM/Clang/LLD based mingw-w64 toolchain
msvc-llvm-nix
mxe - MXE (M cross environment)
music-vibes - Desktop app for translating audio output into vibrations
project-azua - Data Efficient Decision Making
cargo-xwin - Cross compile Cargo project to Windows MSVC target with ease
BinaryBuilder.jl - Binary Dependency Builder for Julia
xlsxwriter-rs - Excel file writer for Rust