Use hybrid CRT linkage instead of full static #5913
Merged
+14
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
florelis
approved these changes
Dec 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See https://aka.ms/hybridcrt for additional details.
When building ReleaseStatic, use the hybrid linkage model. This produces a binary that is closer in size to the dynamic linkage than the full static, relying on the UCRT binary that ships in Windows to provide the core CRT functionality. As an example, the WindowsPackageManager.dll is ~90 KB larger as hybrid than dynamic, but is another ~160 KB larger as static than hybrid.
Microsoft Reviewers: Open in CodeFlow