Details
-
Bug
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
5.0.0
-
None
Description
At Deployment in Visual C++ we learn that one could deploy the Visual C++ runtime in three ways:
- Central deployment
- Local deployment
- Static linking
There we have the advice:
Central deployment by using a Redistributable package enables Windows Update to automatically update the Visual C++ libraries. For continued security and functionality, we recommend that you use the library DLLs in your application instead of static libraries, and use Redistributable packages and central deployment instead of local deployment.
That's what we are doing, right. Using the vcredist packages.
But we deliver packages from 2014 and 2019!
Note that the vcredist contains the Visual C++ Runtime which is ABI compatible for different versions.
My Visual Studio 2022 redist directory has packages from 2024.
We need to keep update the vcredist packages, not only due to security fixes that happen in the meantime, but also for not shipping outdated software that nobody needs.
Note that one can have local deployment for Visual C++ by having one CMake line in their CMakeLists.txt
include(InstallRequiredSystemLibraries)
which then will get more up to date Visual C++ Runtime DLLs because the compiler is updated more frequent on the build machine!
Attachments
Gerrit Reviews
For Gerrit Dashboard: QTBUG-133787 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
578849,2 | QtCreator: Do not install 32bit or MSVC2010 vcredist anymore | production | qtsdk/tqtc-qtsdk | Status: DEFERRED | -1 | 0 |