-
-
Notifications
You must be signed in to change notification settings - Fork 1.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 MSIs built with CMake do not install MSVC runtime #10079
Comments
Commented by: uklotzde Didn't we upgrade the build VM to MSVC 2017 (15.0)? Then MSVC 2015 (14.0) are the wrong redistributables. |
Commented by: uklotzde This could also be the reason for the failing 2.3.0 WiX builds. |
Commented by: Be-ing
|
Commented by: uklotzde On AppVeyor we also use the "Visual Studio 2017" image. |
Commented by: uklotzde Sorry for the confusion, Microsoft versioning. At least the buildserver seems to bundle the correct versions into 2.3-j00019-x86-release-fastbuild-static-55e94982-minimal.zip according to build_environment.log:
The SDK version is still 14, while the internal MSVC version is 15. |
Commented by: uklotzde https://docs.microsoft.com/cpp/porting/binary-compat-2015-2017 |
Commented by: Be-ing Are you confusing this with Bug #1814273? That was with the legacy SCons build. This bug is about CMake. The CMake builds do not package any version of the MSVC runtime. |
Commented by: uklotzde I didn't notice that we already have a bug for the redistributable versioning issue. Added a note there. |
Commented by: JosepMaJAZ Correct. It is a pending task to regenerate the CMake installer with all that the Scons script did, which includes generating multilanguage installer (which require a cumbersome multi-installer generation) and the generation of the exe installer that was a container of both, the runtime and mixxx installers. And we might include visual studio 2017 or 2019 runtime now ( the are all downward compatible to 2015). If we include 2017, we will probably need some workaround precisely for the bug reported on that bug #1814273 . |
Issue closed with status Fix Released. |
Reported by: Be-ing
Date: 2020-08-09T18:24:42Z
Status: Fix Released
Importance: Critical
Launchpad Issue: lp1890955
The code execution could not proceed because MSVCP140.dll was not found. Reinstalling the program may fix this problem.
After clicking OK on that dialog, another one appears:
The code execution cannot proceed because VCRUNTIME140.dll was not found. Reinstalling the program may fix this problem.
After installing the MSVC runtime separately, Mixxx starts successfully.
The text was updated successfully, but these errors were encountered: