-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows nightlies have statically linked rustc/rustdoc binaries #13491
Labels
O-windows
Operating system: Windows
Comments
This appears to be because we install from stage3 on windows, which is hard-wired to produce statically linked binaries because I thought stage3 was only used for snapshots. |
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Apr 14, 2014
In the past, windows was installed from stage3 to guarantee convergence between the host and target artifacts, but syntax extensions on all platforms are currently relying on convergence, so special casing this one platform has become less relevant over time. This will also have the added benefit of dealing with rust-lang#13474 and rust-lang#13491. These issues will be closed after next next nightly is confirmed to fix them.
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Apr 16, 2014
In the past, windows was installed from stage3 to guarantee convergence between the host and target artifacts, but syntax extensions on all platforms are currently relying on convergence, so special casing this one platform has become less relevant over time. This will also have the added benefit of dealing with rust-lang#13474 and rust-lang#13491. These issues will be closed after next next nightly is confirmed to fix them.
Closed by efec34a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
They're around 40MB in size, which would be ridiculously large for a dynamically linked binary.
I've confirmed that the OSX/linux nightlies are indeed dynamically linked.
The text was updated successfully, but these errors were encountered: