[CMake] cpack install problem
Bill Hoffman
bill.hoffman at kitware.com
Thu Sep 3 16:36:14 EDT 2009
John Drescher wrote:
> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
> <dependency>
> <dependentAssembly>
> <assemblyIdentity type="win32" name="Microsoft.VC80.CRT"
> version="8.0.50727.762" processorArchitecture="x86"
> publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
> </dependentAssembly>
> </dependency>
> <dependency>
> <dependentAssembly>
> <assemblyIdentity type="win32" name="Microsoft.VC80.CRT"
> version="8.0.50727.4053" processorArchitecture="x86"
> publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
> </dependentAssembly>
> </dependency>
> <dependency>
> <dependentAssembly>
> <assemblyIdentity type="win32" name="Microsoft.VC80.CRT"
> version="8.0.50608.0" processorArchitecture="x86"
> publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
> </dependentAssembly>
> </dependency>
>
The fix is to rebuild everything with the same version (SP) of visual
studio. A single exe should not have more than one of these things in
it. If it does then you have to do the redist thing. If it only has
one, which is possible, then you can ship the libraries and not have to
install into the system with redist. If there is one .obj or one .dll
that was built with a slight different version of VS, then you get this
problem, and the side by side manifest will not work. The redist.exe
works by installing all of them into the system. It requires
administrator rights to do this, and installs them for the whole computer.
-Bill
More information about the CMake
mailing list