[Qt-interest] Mismatched VC90 CRT versions in manifest file

Michael Jackson mike.jackson at bluequartz.net
Thu Jan 28 19:21:46 CET 2010


On 1/28/10 1:09 PM, in article 4B61D2C2.6030801 at thesmithfam.org, "Dave
Smith" wrote:

> David Ching wrote:
>> Just to make crystal clear, no matter what version of VS was used to build
>> Qt, and what version of VS was used to build your .exe,
>> 
>>   1) They must be binded to the same version of the redists
>>   2) Those redists must be on the target system.  A fresh XP install doesn't
>> have those redists.  So you must install them using one of the methods I
>> said.
>>   
> 
> For 4 years, I have been building and deploying Qt4 apps on Windows XP
> with no problems, using Visual Studio 2008 Express. I used to be able to
> just drop the Microsoft.VC90.CRT folder in my application directory at
> install time and be done with it. As of today, tested with Qt 4.6.1 and
> Qt 4.5.3, this method no longer works for me. I have to install
> vcredist_x86.exe for VS 2008 SP1 prior to running my app or it can't
> find the MSVCR90.dll.
> 
> Perhaps this is the first time I have installed on an absolutely freshly
> installed Windows XP box, but I doubt it.
> 
> Has something changed of late to render this method ineffectual?
> 
> --Dave

Of course, you could live on the edge and NOT apply the security update. I
have the RTM version of Visual Studio and don't have any of these problems.
The way I see it as an individual developer and time is money is that I can
keep up with the MS Security Updates and then have to recompile ALL my
projects and add "special" header files to them to make sure the correct CRT
is found which would take way too much time OR I can NOT install the update
and keep developing the way I have been developing the last few years with
nothing special to be done. I weighed the pros and cons and made my choice.

--
Mike J.




More information about the Qt-interest-old mailing list