Hi,
I downloaded the windows installer build of the 2.55beta. I installed it on my laptop and upon start I received an exception (see attached screen shot). Previous 2.5x alpha/beta's had the same issue. The older 2.49 version never had this issue.
The exception however is known to me and indicates that the files in the windows distribution are not complete. This has to do with the fact that Microsoft's build system assumes the target machine has the visual studio run-times installed, which unfortunately is not always the case.
The solution is simple, add the required libraries to the win32 distribution package and install them in the folder holding the blender.exe. The libraries needed are:
mfc90.dll
mfc90u.dll
mfcm90.dll
mfcm90u.dll
msvcp90.dll
msvcr90.dll
msvcrt.dll
Also, a manifest is needed. I've attached one to this report.
Hope the next release will have this fixed.
Regards,
Ruud
Description
Event Timeline
The installer runs vcredist as part of the installation process, so these files should have been installed to your machine.
The zip distribution has the necessary files. For Blender the correct files to include are: msvcm90.dll, msvcp90.dll, msvcr90.dll, vcomp90.dll and the two manifests for those. The zip already has those, but apparently the vcredist installation doesn't work correctly. On the virtual box Windows 7 install I did (clean install without any other program installed) this worked as expected: without vcredist install fail, with vcredist install (as part of installation process) correct install.
I might opt for including them directly into the installer, like the zip, but I'd prefer not to.
We don't link against mfc libraries, so those are not needed.
I figured it out. I installed as a regular user. The installer did not complain about that. However, installing vcredist can only be done as admin.
The solution here is to make a choice: either let the installer check for being admin so vcredist can run or add the needed dll's manually. The latter being in line with supplying a zipped installation.
Taking the easy way: make sure that dlls are in place before starting 'scons nsis', meaning from next release on we'll just have the DLLs like in the zip release inside install dir.
r33081.
From now on builders will have to add the necessary dlls and manifest files to BF_INSTALLDIR before running scons with the nsis target. BF_VCREDIST will be removed.