Quiche is compiled unconditionally by wind-quic and wind-tuic, including
32-bit targets and --no-default-features builds. There is no quiche Cargo
feature. Quinn remains an optional backend with a separately selected Rustls
crypto provider. Applications still select their backend at runtime.
Building the Quiche backend requires the target's BoringSSL C/C++ toolchain,
CMake and libclang; Windows builds also require NASM. Cross builds need the
corresponding compiler and sysroot. The workspace patches the core quiche,
tokio-quiche and datagram-socket crates to the same pinned Git revision of
rust-proxy/quiche so every backend consumer receives the same portability
fixes. The forks/quiche submodule is the reference and editing checkout.
The naive outbound (crates/wind-naive) uses Chromium Cronet through the
cronet-rs bindings, which need a
libcronet shared library at runtime. To avoid a manual install, build with the
opt-in download feature:
cargo build -p wind --features downloadcronet-sys's build script then fetches the prebuilt matching the target from
rust-proxy/cronet-binaries
into OUT_DIR and verifies its SHA-256 against a pinned checksum. The feature is
off by default so ordinary builds never touch the network. See
crates/wind-naive/README.md for details.
To embed a locally built Cronet archive instead of loading a shared library:
CRONET_LIB_DIR=/path/to/native/lib cargo build -p wind --features naive-staticnaive-static takes precedence over dynamic loading. Use a matching glibc or
musl archive on Linux, or cronet.lib and its generated link_flags.txt on
Windows MSVC. Existing Apple/Android archives also support static linking.
A supplied CRONET_LIB_DIR takes precedence over automatic downloads.
Windows downloads automatically match Rust's CRT. The default /MD archive
needs no extra RUSTFLAGS; it statically links Cronet and uses the MSVC runtime
DLLs. Explicit +crt-static builds select the /MT archive and should also
pass --target. A manually supplied archive must match the application's CRT.
cargo build -p wind --features naive-static,naive-downloadThe download switch does not select a backend. In dynamic mode it keeps
runtime libloading and performs no download. Combined with the static switch it
fetches the target's static archive and verifies SHA-256 before linking.
Static linkage takes precedence when Cargo enables both backends. A supplied
CRONET_LIB_DIR overrides downloading. The legacy download feature retains
its existing behavior.
Static archives for Linux (glibc/musl), Windows MSVC, Apple, and Android
are pinned to the static-20261116.1 release with SHA-256 verification.
Custom unpinned assets require CRONET_DOWNLOAD_SHA256. Windows also downloads
the matching .link-flags.txt and requires its pinned checksum or
CRONET_DOWNLOAD_LINK_FLAGS_SHA256.