repairwheel
cargo-zigbuild
repairwheel | cargo-zigbuild | |
---|---|---|
3 | 19 | |
29 | 1,254 | |
- | 4.5% | |
7.1 | 8.6 | |
6 days ago | about 1 month ago | |
Python | Rust | |
MIT License | MIT License |
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.
repairwheel
-
Ask HN: What rabbit hole(s) did you dive into recently?
I got into cross-compiling Python wheels (e.g., building macos wheels on linux and vice versa). Zig's `zig cc` does much of the heavy lifting, but one step in building a portable wheel is the "repair" process which vends native library dependencies into the wheel, necessitating binary patching (auditwheel does this for linux, delocate for macos).
I wanted to be able to do this cross platform, so I re-implemented ELF patching and Mach-O patching and adhoc signing in Python, and wrapped them into a tool called repairwheel: https://github.com/jvolkman/repairwheel
-
Show HN: macOS-cross-compiler ā Compile binaries for macOS on Linux
I'll plug some work I've been doing to (attempt to) enable cross compilation of Python wheels. I put together a small example [1] that builds the zstandard wheel, and can build macos wheels on linux and linux wheels on macos using zig cc.
macos wheels must still be adhoc signed (codesign) and binary patched (install_name_tool), so I re-implemented those functions in Python [2].
[1] https://github.com/jvolkman/bazel-pycross-zstandard-example
[2] https://github.com/jvolkman/repairwheel/tree/main/src/repair...
-
Sunday Daily Thread: What's everyone working on this week?
I mixed auditwheel, delocate, and delvewheel into a single tool called repairwheel and reimplemented all of the required external tools (patchelf, otool, codesign, etc.) in pure python.
cargo-zigbuild
-
Show HN: macOS-cross-compiler ā Compile binaries for macOS on Linux
https://github.com/rust-cross/cargo-zigbuild
Iām curious what the blockers are for rustc to cross-compile like zig does natively.
- Cargo-zigbuild: Compile Rust using Zig as linker for easier cross compiling
- [Review] Introducing cargo-xwin: A Solution for Cross-Compiling Rust on macOS to MSVC
- Compiling Linux to Mac in CI/CD
- cargo-zigbuild 0.16 added support for (cross-)compiling macOS universal2 binaries/libraries
-
Conditional compilation to avoid cross compilation
Perhaps you can try cargo-zigbuild, it uses zig-cc for cross-compilation instead of creating a container, so it should be much more lightweight on MacOS, without all the cost of virtualization and file sharing.
- Cross-compiling simple Rust code from Mac OS X to Raspberry Pi 4
-
Future of Rust, 2023 and beyond?
I have tried, however I haven't been able to get it to work reliably (e.g. building on windows + linux on WSL works, Mac is a lot more involved; tried building for windows + linux on Mac and I couldn't get it to work at all); I've had some luck using zigbuild but that too doesn't seem to work for Mac.
-
C2Rust Transpiler
Zig also takes this approach, and even exposes its C compiler (which if I recall correctly is basically Clang plus diverse sysroots and other customisation out of the box) as a separate `zig cc`.
I do a lot of work in Rust, and cross-compilation can be a pain when you have a lot of C dependencies. Fortunately https://github.com/messense/cargo-zigbuild exists. It sounds crazy, but using Zig's inbuilt C compiler to help build my Rust projects has been the smoothest option I've found.
I can't help but wonder if it would be worth it for Rust to follow D and Zig by shipping its own inbuilt C compiler, even if they still want to also support external C toolchains. It should be roughly the same effort as it was for Zig, given that they both use LLVM.
-
Short story of Rust being amazing yet again (because it compiles on different architectures effortlessly)
Wait until you start using cargo zig-build. Suddenly it becomes way better than Go's cross compiler because you can seamlessly cross-compile rust AND C (thanks to Zig compiler of course). https://github.com/messense/cargo-zigbuild
What are some alternatives?
tensorflow-windows-wheel - Tensorflow prebuilt binary for Windows
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
cibuildwheel - š” Build Python wheels for all the platforms with minimal configuration.
rust.aws-cdk-lambda - A CDK (v2) Construct Library for AWS Lambda in Rust
twine - Utilities for interacting with PyPI
aws-lambda-rust-runtime - A Rust runtime for AWS Lambda
py2exe - Create standalone Windows programs from Python code
serverless-rust-demo - Sample serverless application written in Rust
terminal-typeracer
doom - DOOM translated from C to V.
ci - AppVeyor community support repository
embed-c - Embed C code at compile time inside Rust using C2Rust