[PyQt] PyQt5 installation on Windows

[Phil Thompson]

> On 24 Jan 2016, at 4:47 pm, scott zimmerman <scottz1 at hotmail.com> wrote:
> 
> I believe both of these problems could be fixed by parsing the command line before calling _find_exe.
> The other problem I forgot to mention is that configure.py doesn't find cl.exe and nmake.exe. For some reason the spawned process doesn't inherit the "path" variable from the x64 command prompt window. That could be fixed by adding a new command line option for the compiler tools, e.g. --cpath.

I've never had a problem. It would be better to work out why PATH doesn't get inherited on your system.

Phil

> > Subject: Re: [PyQt] PyQt5 installation on Windows
> > From: phil at riverbankcomputing.com
> > Date: Sun, 24 Jan 2016 16:24:15 +0000
> > CC: pyqt at riverbankcomputing.com
> > To: scottz1 at hotmail.com
> > 
> > On 24 Jan 2016, at 4:07 pm, scott zimmerman <scottz1 at hotmail.com> wrote:
> > > 
> > > Are there plans to fix configure.py so it works on Windows?
> > >  
> > > 1. anaconda appends it's own bin directory to the front of the path returned by os.environ.get in _find_exe. That causes the script to see the old version of qmake.
> > > 2. TargetConfiguration.__init__ is called in main before parsing the command line. Since _find_exe does find an old qmake.exe, it ignores the --qmake option!
> > >  
> > > Running the script from Visual Studio x64 command prompt doesn't work because of #1. Running the script with --qmake doesn't work because of #2.
> > 
> > --qmake isn't even an option when running on Windows. It will use the first qmake on PATH.
> > 
> > Phil