[Paraview] MinGW compilation

[Mike Jackson]

http://www.itwriting.com/blog/?postid=261

explains it way better than me. Basically with VS 6 there was DLL
hell. With VS 7, MS tried to alleviate the problem by saying put all
your DLLs in the same directory as the executable. This alleviated DLL
Hell but MS could NOT centrally admin those c runtime libraries like
they could in VS 6. So they came up with DLL versioning. But to use
this each user has to run an executable that installs the VS 8 Runtime
DLL in system32, which requires admin access. My users don't have
admin rights on their machines. So basically this would require 2
support calls to our computer support department. One to install the
VS8Runtime dlls and another to install ParaView. With VS2003.Net it is
a drag and drop installation, and probably with MinGW.

Hope that explains it. (I have gotten a real education on this today.
You know me, I am an OS X/Linux guy)

Mike

On Thu, Feb 28, 2008 at 3:24 PM, Berk Geveci <berk.geveci at kitware.com> wrote:
> This will probably expose my ignorance about Windows but why can't
> your users install a vs05 build without admin privileges?
>
> -berk
>
>
> On 2/28/08, Mike Jackson <imikejackson at gmail.com> wrote:
> > is anyone using MinGW to compile ParaView cvs? Turns out I only have
> >  the Standard version of VS2003.net so there is no optimization
> >  allowed. I am thinking of alternatives. I have VS2005 Pro except I
> >  really need something that can produce a drag and drop installation.
> >  Our users do not have local admin on their machines to use an actual
> >  installer.
> >
> >  Any comments are most welcome.
> >
> >  Thanks
> >
> > --
> >  Mike Jackson
> >  imikejackson _at_ gee-mail dot com
> >  _______________________________________________
> >  ParaView mailing list
> >  ParaView at paraview.org
> >  http://www.paraview.org/mailman/listinfo/paraview
> >
>



-- 
Mike Jackson
imikejackson _at_ gee-mail dot com