xwin
xlsxwriter-rs
xwin | xlsxwriter-rs | |
---|---|---|
5 | 1 | |
327 | 252 | |
- | - | |
7.4 | 3.8 | |
about 1 month ago | 8 months 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.
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.
xlsxwriter-rs
-
Announcing cargo-xwinbuild: Cross compile Cargo project to Windows msvc target with ease
How set the LIBCLANG_PATH? My exe depend on this config to build https://github.com/informationsea/xlsxwriter-rs
What are some alternatives?
cargo-deny - ❌ Cargo plugin for linting your dependencies 🦀
ExcelJS - Excel Workbook Manager
llvm-mingw - An LLVM/Clang/LLD based mingw-w64 toolchain
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
msvc-llvm-nix
umya-spreadsheet - A pure rust library for reading and writing spreadsheet files
music-vibes - Desktop app for translating audio output into vibrations
libxlsxwriter - A C library for creating Excel XLSX files.
cargo-xwin - Cross compile Cargo project to Windows MSVC target with ease
php-ext-xlswriter - 🚀 PHP Extension for creating and reader XLSX files.
mxe - MXE (M cross environment)
XlsxWriter - A Python module for creating Excel XLSX files.