Likely comes from a build tree produced with an original Visual Studio, then an upgrade to a SP1 (or 2 or 3) of the same Visual Studio, then an incremental build of the tree...<div><br></div><div>Produces some obj files that came from the original, some that came with SP1 and the blend causes dependencies on both versions of the runtime.</div>
<div><br></div><div>If that's the cause, the solution is to do a clean build (of *everything* that you link).<br><br></div><div>It could also be caused by linking in 3rd party binaries that depend on a different version of the runtime than your built binaries. If that's the cause, the solution is again a full rebuild using the same version as your 3rd party binaries.</div>
<div><br></div><div>If that's not possible, for whatever reason, then I'm not sure what the solution is.... :-(</div><div><br></div><div><br><div class="gmail_quote">On Thu, Sep 3, 2009 at 3:21 PM, Dean Inglis <span dir="ltr"><<a href="mailto:dean.inglis@camris.ca">dean.inglis@camris.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Bill,<br>
<br>
within the exe there appear to be two versions:<br>
<br>
<dependency><br>
<dependentAssembly><br>
<assemblyIdentity type="win32" name="Microsoft.VC80.CRT"<br>
version="8.0.50727.4053" processorArchitecture="x86"<br>
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity><br>
</dependentAssembly><br>
</dependency><br>
<dependency><br>
<dependentAssembly><br>
<assemblyIdentity type="win32" name="Microsoft.VC80.CRT"<br>
version="8.0.50727.762" processorArchitecture="x86"<br>
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity><br>
</dependentAssembly><br>
</dependency><br>
</assembly><br>
<br>
Not sure what to do to correct this. Why would the linker/compiler<br>
embed two different assembly identities?<br>
<font color="#888888"><br>
Dean<br>
</font><div><div></div><div class="h5"><br>
-----Original Message-----<br>
From: Bill Hoffman [mailto:<a href="mailto:bill.hoffman@kitware.com">bill.hoffman@kitware.com</a>]<br>
Sent: September-03-09 2:38 PM<br>
To: <a href="mailto:dean.inglis@camris.ca">dean.inglis@camris.ca</a><br>
Cc: <a href="mailto:cmake@cmake.org">cmake@cmake.org</a><br>
Subject: Re: [CMake] cpack install problem<br>
<br>
Dean Inglis wrote:<br>
> Hi,<br>
> I originally posted this thread to kwwidgets, but have<br>
> not had much success and perhaps this is a cpack/cmake<br>
> issue Im having.<br>
><br>
><br>
> I¹m building stand alone applications using VTK, ITK, GDCM, KWWidgets and<br>
I<br>
> I'm recently having problems getting my apps to run on windows (XP, Vista<br>
32<br>
> bit) platforms where the installer is generated by cpack (NSIS). The<br>
> apps/toolkits tcl/tk are all statically built and linked in Release mode<br>
> using MS Visual Studio Express 2005. I am compiling using the command<br>
line<br>
> tools (nmake). I keep getting:<br>
><br>
> The application has failed to start because its side-by-side<br>
> configuration is incorrect. Please see the application event log for<br>
more<br>
> detail.<br>
><br>
> Installing vcredist_x86.exe does not help as was<br>
> suggested on some MS forums. As an example, the installer installs<br>
> C:\Program Files\MyApp\bin\myKWWidgetsApp.exe<br>
> C:\Program Files\MyApp\bin\Microsoft.VC80.CRT.manifest<br>
> C:\Program Files\MyApp\bin\ msvcm80.dll<br>
> C:\Program Files\MyApp\bin\ msvcp80.dll<br>
> C:\Program Files\MyApp\bin\ msvcr80.dll<br>
><br>
> If I run the windows Event Viewer and look at the error:<br>
><br>
> "Activation context generation failed for<br>
> "C:Users\Student\Documents\MyApp\bin\myKWWidgetsApp.exe". Error in<br>
manifest<br>
> or policy file "" on line. A component version required by the<br>
application<br>
> conflicts with another component version already active. Conflicting<br>
> components are: Component 1: C:\Windows\WinSxS\manifests\x86<br>
> microsoft.vc80.crt 1fc8b3b9a1e18e3b<br>
> 8.0.50727.3053_none_d08d7bba442a9b36.manifest. Component 2: C:\Program<br>
> Files\ MyApp\bin\Microsoft.VC80.CRT.MANIFEST.<br>
><br>
><br>
> Any ideas on how to fix or sort this out would be great, thanks<br>
><br>
<br>
Pull up myKWWidgetsApp.exe in text editor and look for the embeded<br>
manifest xml. Just search for xml. See if it has two version of the<br>
run time libraries it wants. If so, you are linking in something that<br>
uses two different version of the run time.<br>
<br>
-Bill<br>
<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br></div>