Revisiting the conversation in #319 trying to follow up on the point I raised concerning the CRT linkage, I realized one of the first questions asked was if we can just link all vcpkg dependencies statically (before that whole conversation got sidetracked to pointless license discussions).
Since vcpkg already has a triplet for static ports using dynamic CRT linkage, this will just do that.
Related Issues
Screenshots (if applicable)
Checklist
[x] I have tested my changes locally and verified that they work as intended.
[x] I have documented any new or modified functionality.
[x] I have reviewed the changes to ensure they do not introduce any unnecessary complexity or duplicate code.
[x] I understand that by submitting this pull request, I am agreeing to license my contributions under the project's license.
Additional Comments
If we go for this PR instead of #319, we should still take the change from 8f670d7f0d95ea38fa7efb369394d947070251fb of that PR. Already in main as part of 82c04f8fb925f74ac045b5c4510d890ecfbf19c8.
Pull Request Type
Description
Revisiting the conversation in #319 trying to follow up on the point I raised concerning the CRT linkage, I realized one of the first questions asked was if we can just link all vcpkg dependencies statically (before that whole conversation got sidetracked to pointless license discussions). Since vcpkg already has a triplet for static ports using dynamic CRT linkage, this will just do that.
Related Issues
Screenshots (if applicable)
Checklist
Additional Comments
If we go for this PR instead of #319, we should still take the change from 8f670d7f0d95ea38fa7efb369394d947070251fb of that PR.Already in main as part of 82c04f8fb925f74ac045b5c4510d890ecfbf19c8.