#msvc #windows-msvc #windows #vcruntime

no-std build static_vcruntime

Statically link the VCRuntime when using the MSVC toolchain

10 stable releases

2.0.0 Apr 20, 2022
1.5.1 Apr 23, 2021
1.1.0 Mar 30, 2021

#147 in Build Utils

Download history 592/week @ 2023-12-15 465/week @ 2023-12-22 710/week @ 2023-12-29 1006/week @ 2024-01-05 862/week @ 2024-01-12 770/week @ 2024-01-19 616/week @ 2024-01-26 781/week @ 2024-02-02 1054/week @ 2024-02-09 1313/week @ 2024-02-16 1067/week @ 2024-02-23 1282/week @ 2024-03-01 1964/week @ 2024-03-08 1834/week @ 2024-03-15 1668/week @ 2024-03-22 1494/week @ 2024-03-29

7,124 downloads per month
Used in 8 crates

MIT OR Apache-2.0 OR Zlib

8KB

Statically link the VCRuntime when using the MSVC toolchain.

By default, Rust requires programs to deploy vcruntime140.dll (or equivalent) when redistributing binaries. This crate statically links the library instead.

Usage

Add this to your Cargo.toml:

[build-dependencies]
static_vcruntime = "2.0"

And in your build script:

fn main() {
    static_vcruntime::metabuild();
}

That is all. Then when you build a release binary, the runtime will be statically linked:

cargo build --release

Issues

If you have problems then you may need to clean the build directory before rebuilding:

cargo clean

If all else fails then, in the same directory as your Cargo.toml, create a folder called .cargo. In that folder create the file config.toml and add the following:

[target.'cfg(all(windows, target_env = "msvc"))']
rustflags = ["-C", "target-feature=+crt-static"]

This makes it easier to override the defaults.

No runtime deps