ParaView should package correctly such that its installer works on any Windows system, regardless of MSVC runtime dlls. That is what the line:<br>INCLUDE(InstallRequiredSystemLibraries)<br>from ParaView3CPack.cmake is all about.<br>
<br>With VS8 2005, you can still put all the dlls in the same directory with the app, but you also need a manifest file. CMake 2.4.8 should properly take care of this for you, though.<br><br>If not, it's a CMake bug. (Or a bug in ParaView's cmakelists files...)<br>
<br>Are you trying to build an installer after building with VS8 and it's not working?<br><br>HTH,<br>David<br><br><br><div><span class="gmail_quote">On 2/28/08, <b class="gmail_sendername">Berk Geveci</b> <<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ah, I see. I think there is a way of packaging the vs05 dlls without<br> requiring the users to install the Microsoft dlls themselves. It has<br> something to do with manifests and such. Dave Cole would know better.<br> <br>
<br> -berk<br> <br> On 2/28/08, Mike Jackson <<a href="mailto:imikejackson@gmail.com">imikejackson@gmail.com</a>> wrote:<br> > <a href="http://www.itwriting.com/blog/?postid=261">http://www.itwriting.com/blog/?postid=261</a><br>
><br> > explains it way better than me. Basically with VS 6 there was DLL<br> > hell. With VS 7, MS tried to alleviate the problem by saying put all<br> > your DLLs in the same directory as the executable. This alleviated DLL<br>
> Hell but MS could NOT centrally admin those c runtime libraries like<br> > they could in VS 6. So they came up with DLL versioning. But to use<br> > this each user has to run an executable that installs the VS 8 Runtime<br>
> DLL in system32, which requires admin access. My users don't have<br> > admin rights on their machines. So basically this would require 2<br> > support calls to our computer support department. One to install the<br>
> VS8Runtime dlls and another to install ParaView. With VS2003.Net it is<br> > a drag and drop installation, and probably with MinGW.<br> ><br> > Hope that explains it. (I have gotten a real education on this today.<br>
> You know me, I am an OS X/Linux guy)<br> ><br> ><br> > Mike<br> ><br> ><br> > On Thu, Feb 28, 2008 at 3:24 PM, Berk Geveci <<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>> wrote:<br>
> > This will probably expose my ignorance about Windows but why can't<br> > > your users install a vs05 build without admin privileges?<br> > ><br> > > -berk<br> > ><br> > ><br>
> > On 2/28/08, Mike Jackson <<a href="mailto:imikejackson@gmail.com">imikejackson@gmail.com</a>> wrote:<br> > > > is anyone using MinGW to compile ParaView cvs? Turns out I only have<br> > > > the Standard version of VS2003.net so there is no optimization<br>
> > > allowed. I am thinking of alternatives. I have VS2005 Pro except I<br> > > > really need something that can produce a drag and drop installation.<br> > > > Our users do not have local admin on their machines to use an actual<br>
> > > installer.<br> > > ><br> > > > Any comments are most welcome.<br> > > ><br> > > > Thanks<br> > > ><br> > > > --<br> > > > Mike Jackson<br>
> > > imikejackson _at_ gee-mail dot com<br> > > > _______________________________________________<br> > > > ParaView mailing list<br> > > > <a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br>
> > > <a href="http://www.paraview.org/mailman/listinfo/paraview">http://www.paraview.org/mailman/listinfo/paraview</a><br> > > ><br> > ><br> ><br> ><br> ><br> ><br> > --<br> ><br>
> Mike Jackson<br> > imikejackson _at_ gee-mail dot com<br> ><br> _______________________________________________<br> ParaView mailing list<br> <a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br>
<a href="http://www.paraview.org/mailman/listinfo/paraview">http://www.paraview.org/mailman/listinfo/paraview</a><br> </blockquote></div><br>