Did you try the dependency walker (available via google) to see if there may be any dll's you need to have in the same directory as the binary? <br><br>Regards,<br><br>Juan<br><br><div class="gmail_quote">On Thu, Aug 20, 2009 at 5:03 PM, Mike Jackson <span dir="ltr"><<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">So I "created" the proper paths within the VCExpress installation and<br>
placed the downloaded vcredist_x86.exe file in there. CMake found it.<br>
NSIS found it and included it. I ran my new installer on a "clean" XP<br>
SP3 machine. Verified the vcredist.exe actually ran also. Tried to<br>
launch an application and I still get an error that says the<br>
application is not configured correctly.<br>
<br>
Still lost and Confused.<br>
<font color="#888888"><br>
Mike<br>
</font><div class="im"><br>
On Thu, Aug 20, 2009 at 5:40 PM, j s<<a href="mailto:j.s4403@gmail.com">j.s4403@gmail.com</a>> wrote:<br>
</div><div><div></div><div class="h5">> I don't believe that to be the case with Visual Express 2008. I don't know<br>
> how previous editions work.<br>
><br>
> Can I use Express Editions for commercial use?<br>
><br>
> Yes, there are no licensing restrictions for applications built using Visual<br>
> Studio Express Editions.<br>
><br>
> <a href="http://www.microsoft.com/express/support/faq/" target="_blank">http://www.microsoft.com/express/support/faq/</a><br>
><br>
> Juan<br>
><br>
><br>
><br>
> On Thu, Aug 20, 2009 at 4:33 PM, David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>> wrote:<br>
>><br>
>> Hold on there...<br>
>> The Express editions are not meant to build redistributable binaries.<br>
>> They're meant for personal use: i.e. -- each user compiles his own code. I'm<br>
>> pretty sure it's a violation of the Express edition license agreement to<br>
>> build binaries for other people. You need at least the "Standard" edition of<br>
>> VS to get that capability.<br>
>><br>
>><br>
>> HTH,<br>
>> David<br>
>><br>
>> On Thu, Aug 20, 2009 at 5:11 PM, Mike Jackson<br>
>> <<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>> wrote:<br>
>>><br>
>>> On Thu, Aug 20, 2009 at 4:06 PM, James Bigler<<a href="mailto:jamesbigler@gmail.com">jamesbigler@gmail.com</a>><br>
>>> wrote:<br>
>>> > On Thu, Aug 20, 2009 at 1:51 PM, Mike Jackson<br>
>>> > <<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>><br>
>>> > wrote:<br>
>>> >><br>
>>> >> On Thu, Aug 6, 2009 at 3:12 PM, Marcus D. Hanwell<<a href="mailto:marcus@cryos.org">marcus@cryos.org</a>><br>
>>> >> wrote:<br>
>>> >> > James Bigler wrote:<br>
>>> >> >> On Thu, Aug 6, 2009 at 12:10 PM, Bill Hoffman<br>
>>> >> >> <<a href="mailto:bill.hoffman@kitware.com">bill.hoffman@kitware.com</a> <mailto:<a href="mailto:bill.hoffman@kitware.com">bill.hoffman@kitware.com</a>>> wrote:<br>
>>> >> >><br>
>>> >> >> James Bigler wrote:<br>
>>> >> >><br>
>>> >> >><br>
>>> >> >> Well, I was using VS 2005 64 bit with SP 1. I wonder if<br>
>>> >> >> there<br>
>>> >> >> is a similar bug or if there is something else going wrong<br>
>>> >> >> such as what Marcus Hanwall described.<br>
>>> >> >><br>
>>> >> >><br>
>>> >> >> I am not sure what your issue is, but I know I have done this<br>
>>> >> >> many<br>
>>> >> >> times...<br>
>>> >> >><br>
>>> >> >> -Bill<br>
>>> >> >><br>
>>> >> >><br>
>>> >> >> I checked the version numbers of the DLLs, and even checked the<br>
>>> >> >> md5sum<br>
>>> >> >> and everything was the same between the dlls in the WinSxS folder<br>
>>> >> >> and<br>
>>> >> >> the ones I'm distributing. It failed on two clean systems without<br>
>>> >> >> the<br>
>>> >> >> vcredist install. I guess I'll run vcredist as Microsoft suggests<br>
>>> >> >> and<br>
>>> >> >> see if I can trouble shoot later.<br>
>>> >> >><br>
>>> >> >> It is a rather perplexing problem.<br>
>>> >> >><br>
>>> >> > The link Bill supplied has all of the relevant information. In the<br>
>>> >> > "Community Discussion" section the second comment provides three<br>
>>> >> > possible workarounds. We are using the third of those when<br>
>>> >> > distributing<br>
>>> >> > Avogadro packages for Windows. The version mismatch in the manifests<br>
>>> >> > of<br>
>>> >> > the compiled executables and the manifest with the redistributable<br>
>>> >> > DLLs<br>
>>> >> > is what causes the issue.<br>
>>> >> ><br>
>>> >> > It seems that MS has no intention of fixing this issue. We have a<br>
>>> >> > clean<br>
>>> >> > VM where we test new installers, as occasionally this change was<br>
>>> >> > lost<br>
>>> >> > and the DLLs failed to load.<br>
>>> >> ><br>
>>> >> > Marcus<br>
>>> >><br>
>>> >> Ok, so I too have run into this problem. What is anyone doing to get<br>
>>> >> around this issue?<br>
>>> >><br>
>>> >> I would really like a solution that did NOT involve editing anything<br>
>>> >> from VC++ install as I would have to pass those instructions on to the<br>
>>> >> next Developer. Clinton's posting about including the VCRedist.exe in<br>
>>> >> the NSIS installer is OK by me. Is that what everyone else is doing?<br>
>>> >><br>
>>> >> Thanks<br>
>>> >> --<br>
>>> >> Mike Jackson<br>
>>> ><br>
>>> > I ended up linking against the static CRT library (/MT), but that's not<br>
>>> > for<br>
>>> > everyone.<br>
>>> > <a href="http://msdn.microsoft.com/en-us/library/ms235460.aspx" target="_blank">http://msdn.microsoft.com/en-us/library/ms235460.aspx</a><br>
>>> ><br>
>>> > My next choice was going to be including the VCRedist.exe in the<br>
>>> > installer.<br>
>>> > For some of the other projects at my company, this is what they do.<br>
>>> ><br>
>>> > Here are some links I've been consulting on the subject of CRT library<br>
>>> > (conflicts with multiple CRTs).<br>
>>> ><br>
>>> > <a href="http://stackoverflow.com/questions/1075050/howto-multiple-versions-of-msvcrt9-as-private-sxs-assemblies" target="_blank">http://stackoverflow.com/questions/1075050/howto-multiple-versions-of-msvcrt9-as-private-sxs-assemblies</a><br>
>>> ><br>
>>> > <a href="http://tedwvc.wordpress.com/2009/08/10/avoiding-problems-with-vc2005-sp1-security-update-kb971090/" target="_blank">http://tedwvc.wordpress.com/2009/08/10/avoiding-problems-with-vc2005-sp1-security-update-kb971090/</a><br>
>>> ><br>
>>> > <a href="http://stackoverflow.com/questions/1265792/visual-studio-2005-security-updates-and-crt-dll-versions-in-manifest" target="_blank">http://stackoverflow.com/questions/1265792/visual-studio-2005-security-updates-and-crt-dll-versions-in-manifest</a><br>
>>> ><br>
>>> > James<br>
>>> ><br>
>>><br>
>>> thanks for the links. Now my head is really spinning. I have VC2008<br>
>>> Express installed on WinXP SP3 and evidently the vcredist.exe is NOT<br>
>>> included with that version? At least I can not find it. So I guess I<br>
>>> have to download it from MSDN (duh) and then manually set all the<br>
>>> paths and all that in oder to have cmake/NSIS find and include it in<br>
>>> the installer. And I thought deploying on OS X was a bit obtuse...<br>
>>><br>
>>> Mike<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>