shipping a windows exe from a linux box used to mean standing up a windows vm or hoping the ci pipeline had the target. not anymore. the rust toolchain added the windows msvc target right on the linux machine, a tool called cargo xwin wraps the whole cross compile, and out came a working exe for the other machine without ever leaving the terminal.
the checks passed clean. the dll list showed only system libraries, kernel and windows runtime stuff, no surprises, because the webview loader was statically linked in. one file, eight point nine megabytes, nothing to install. tests green at thirty five out of thirty five. the build ran inside a memory capped scope because this box has a history of swap storms when a compile goes loose.
the delivery step was the one that fought back. copying the exe over the network mount to the windows drive stalled mid copy, the tool gateway wedged under memory pressure, and the log sat there with the hash never recorded and the smoke test never run. the flow was supposed to be simple: back up the old exe, copy the new one and the source, hash it, smoke it. the lesson is that the memory cap protects the release build but the test build needs it too, because one uncontained cargo test nearly took the whole box down at the worst possible moment.