[PyQt] Re: PyQt 4.4.2 GPL installer / missing DLL

[Phil Thompson]

On Sunday 25 May 2008 10:15:51 am Pierre Raybaut wrote:
> > Date: Sat, 24 May 2008 14:49:33 +0200 From: Thorsten Kampe
> > <thorsten at thorstenkampe.de> Subject: [PyQt] Re: PyQt 4.4.2 GPL
> > installer / missing DLL To: pyqt at riverbankcomputing.com Message-ID:
> > <g192tv$ftg$1 at ger.gmane.org> Content-Type: text/plain; charset="utf-8"
> > * Python(x,y) (Sat, 24 May 2008 09:33:00 +0200)
> >
> >> > Phil Thompson a écrit :
> >>> > > On Friday 23 May 2008 6:47:11 pm Pierre Raybaut wrote:
> >>>> > >> About this missing DLL issue, the main difference between the
> >>>> > >> 4.3.3 and 4.4.x Windows installer releases seems to be about the
> >>>> > >> .dll management. Apparently, since 4.4.1 release, for example,
> >>>> > >> there is not only a QtCore.pyd file but also a QtCore4.dll and so
> >>>> > >> on. Hence the new "add to path" installer feature, for Windows to
> >>>> > >> find the QtCore4.dll. The problem is that MATLAB for example is
> >>>> > >> also using a QtCore4.dll (which is built with MSVS2005, hence the
> >>>> > >> missing MSVCP80.dll error), and Windows find the MATLAB directory
> >>>> > >> first when searching the PATH environment variable... so, PyQt is
> >>>> > >> currently not compatible with MATLAB for example, which is quite
> >>>> > >> a serious problem for me and a lot of scientific users I know.
> >>>> > >> Unless you have a solution to this PATH conflicting issue?
> >>> > >
> >>> > > Just add a .bat file around one of them with a specific PATH set
> >>> > > up.
> >> >
> >> > in order to run MATLAB with a specific PATH set up?
> >> > If that's what you meant, I really can't do that for two reasons.
> >
> > I had this problem, too (just not with Matlab). I copied the DLLs to the
> > site-packages/PyQt4 folder. Not a clean solution but it works. Another
> > possibility would be to /move/ the exes and DLLs to the pyd folder. But
> > then Qt Assistant might not find the help files.
> >
> > Thorsten
>
> Thanks Thorsten, good to know.
> If it works, why not doing it directly in the PyQt4 GPL installer, Phil?
> In fact, that would be great if the "add directory to PATH" thing would
> not be necessary any more, just like before (with the 4.3.3 release).

The previous installer was buggy in this respect. If you chose a different 
installation directory then things tended not to work. With the current 
installer things should still work no matter what the installation directory 
is. That's the behaviour that most people want.

If I were you I'd ignore the PyQt installer (in the same way I ignore the Qt 
installer) and install PyQt from your own installer in a way that suits your 
users.

Things might change with Python v2.6 which will be built with MSVC 2008. I 
will probably include a copy of Qt built using the same compiler (so that the 
phonon module will be supported) instead of the MinGW compiled version from 
Trolltech. I'm not sure if the use of manifests will avoid the problem.

Phil