Menu

Shipping One Rust Codebase to Windows, macOS and Linux: Universal Binaries, Vendored OpenSSL, musl and a Gated Signing Step
📰

Shipping One Rust Codebase to Windows, macOS and Linux: Universal Binaries, Vendored OpenSSL, musl and a Gated Signing Step

DEV Community: rust·c-wind·6 days ago
#FTa2eB7G
#devtorust#devto#dev#build#mist
Reading 0:00
15s threshold

Originally published on MistLab . Part 8 of Building an SSH Terminal .

Part 8 of "Building an SSH Terminal". Workflow and code excerpts are from MistTerm v1.2.26, an open-source (AGPL) SSH terminal client by MistLab, mainly .github/workflows/build.yml ; they are trimmed, and comments are translated from Chinese.

TL;DR

Shipping one Rust codebase to Windows, macOS and Linux takes more than compiling. MistTerm vendors OpenSSL on Windows and macOS, merges arm64 and x86_64 builds into a universal macOS binary with lipo , measures the real glibc requirement from the built binaries, and ships a static musl CLI for older servers. Signing runs in a separate job that needs a maintainer's approval.

Rust compiles to all three desktop platforms, but "compiles" and "ships" are different problems. An SSH client links a C crypto library, needs native installers, has to satisfy macOS code signing and notarization, and should run on servers that are years older than the CI image.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.