[Paraview] MinGW compilation

[Mike Jackson]

I didn't have all the information when I posted that. What is
happening is that I did the install and then put my plugin into the
"plugins" folder (which I made because I thought I needed it).
Launching paraview, paraview then looks in the plugins folder for
stuff to load. Problem is that the crt dlls are really one directory
up, and so the load fails.
  So to be clear, ParaView run without a problem. Loading a plugin
from the "plugins" directory did NOT work because of lack of crt dlls
at the same level as the plugin.

I confirmed this by moving the plugin to the bin directory, launchin
paraview, then manually loading the plugin. That worked just fine.
Unfortunately I really need to have the plugin loaded automatically so
I think I will just adjust the PV source to look in the bin directory
for the plugins.

Mike

On Wed, Mar 5, 2008 at 2:27 PM, David Cole <david.cole at kitware.com> wrote:
> What CRT dlls are being complained about?
> Are there any CRT dlls in the same directory with paraview.exe?
> Is there a manifest file there?
>
> Building the INSTALL project should have the same net effect as building an
> installer with cpack and then running that installer...
>
>
>
>
> On 3/5/08, Mike Jackson <imikejackson at gmail.com> wrote:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Feb 28, 2008, at 6:30 PM, David Cole wrote:
> >
> > On 2/28/08, Mike Jackson <imikejackson at gmail.com> wrote:
> >
> > > The installer that gets created with cpack. Can the user run that
> > > without admin privs?
> >
> >
> > Pre-Vista, yes, installs to "My Documents" for that user. On Vista, no,
> admin is required to run the installer.
> >
> >
> >
> > > Also I was under the impression that NOT every
> > > computer has the VS 8 runtime dlls, that is why there was a
> > > redistributable installer for them. Maybe I just mis-understood
> > > something.
> >
> >
> > NOT every computer does, but they will be installed by the installer that
> CPack builds, right next to paraview.exe. This is your own local copy of the
> dlls instead of installing them to the windows sys dir with the
> redistributable installer. Both techniques work.
> >
> > What you can do is build the installer, then install it somewhere yourself
> (with or without admin on XP or earlier, with admin on Vista) and then take
> that whole install tree and it should be drag-n-drop copyable (with the MSVC
> runtime dlls inside the tree) to somewhere else and it should all work.
> >
> > Having said that, I've not actually done this myself with ParaView, but I
> semi-frequently do it with CMake builds on Windows... I don't think there is
> anything in ParaView that would preclude this technique. You could try it
> with our pre-built windows installer. Install it somewhere on a machine and
> then copy the whole tree to some other location or even another Windows
> machine and see if you can run PV as you expect.
> >
> > Let me know if you run into something that seems odd or doesn't work. It
> should work.
> >
> >
> > Dave
> >
> >
> >
> > So I got everything compiled, and I ran the "INSTALL" project from within
> VS2005 and had it install everything to a local directory. Seems that taking
> that installation location and moving it to another computer is not allowing
> it to work as I still get complaints about the crt dlls. So how do I run
> cpack on paraview? I guess I really need to make the installer, then install
> to a local directory. Does the installer do something special with the
> executable and the manifest file?
> >
> >
> >
> >
> >
> > --
> > Mike Jackson   Senior Research Engineer
> > Innovative Management & Technology Services
> >
> >
> >
> >
> > _______________________________________________
> > ParaView mailing list
> > ParaView at paraview.org
> > http://www.paraview.org/mailman/listinfo/paraview
> >
> >
>
>



-- 
Mike Jackson
imikejackson _at_ gee-mail dot com