Fwd: Need support for pyqtdeploy - search for 'nmake'

[Phil Thompson]

On 20/11/2024 11:07, Wolfgang wrote:
> Dear Phil,
> 
> amazing your fast response ...
> 
> I added the verbose flag and obviously received much more information:
> 
> 
> 
> The script stopped while searching for 'nmake', but I still can not
> see where I've to look for this executable.

It's part of MSVC.

> -------- Weitergeleitete Nachricht --------
> Betreff: 	Re: Need support for pyqtdeploy
> Datum: 	Wed, 20 Nov 2024 10:46:48 +0000
> Von: 	Phil Thompson <phil at riverbankcomputing.com>
> An: 	Dr. Wolfgang Schilling <wschill at freenet.de>
> Kopie (CC): 	pyqt at riverbankcomputing.com
> 
> 
> 
> On 20/11/2024 10:38, Dr. Wolfgang Schilling wrote:
>> Dear Phil!
>> 
>> Thank you for your fast response and help!
>> 
>> I decided to return to MSVC V16, setting it up with "vcvars64.bat" and
>> now, verifying host and target architecture seem to work:
>> 
>> Next steps were to install a perl-Version (and add it to the windows
>> PATH), SIP and PyQt-builder. Then I tried again build-demo.py (with
>> option --target):
>> 
>> It seems to me that the script is searching for a different make file
>> (could not find 'nmake' - I apologize German wording ...). I suggest,
>> 'qmake.exe', which is part of the Python site packages
>> (..\Python\Lib\site-packages\qt5_application\Qt\bin\qmake.exe), would
>> be the correct choice, right?
> 
> No. nmake and qmake are completely different things.
> 
>> I suggest, I need to modify something in the pyqtdeploy suite now?
>> Please, can you help me out how to do it? Can I expect further
>> surprises?
> 
> Use the --verbose flag to see what is going on.
> 
> Phil
> 
>> -------- Weitergeleitete Nachricht --------
>> 
>> BETREFF:
>> Re: Need support for pyqtdeploy
>> 
>> DATUM:
>> Tue, 19 Nov 2024 12:09:38 +0000
>> 
>> VON:
>> Phil Thompson <phil at riverbankcomputing.com>
>> 
>> AN:
>> Dr. Wolfgang Schilling <wschill at freenet.de>
>> 
>> On 18/11/2024 16:49, Dr. Wolfgang Schilling wrote:
>> 
>>> Dear All!
>>> 
>>> I hope I'm doing the right thing to provide this question to you. If
>>> it's not the correct contact, please let me know.
>> 
>> Please ask questions on the PyQt mailing list.
>> 
>>> I've a developped a Python/PyQt5 application which I want to deploy
>>> to
>>> Windows 10 64bit and Linux 32bit. I found your tool "pyqtdeploy"
>>> which
>>> seems to me the right approach to do so.
>> 
>> Other tools are available, eg. PyInstaller.
>> 
>>> I just started with the demo and have problems to get it up and
>>> running. I've installed VisualStudio v17, implemented the
>>> environment
>>> variable "set VisualStudioVersion=17.12.0". In addition I executed
>>> the
>>> script "vcvarsall.bat amd64_arm64" which ends up with the following
>>> message:
>>> 
>>> All seems fine so far, but when I start your tool with:
>>> 
>>> python build-demo.py --target win-64
>>> 
>>> the command stopped with following message:
>>> 
>>> Does that really mean the latest MSVC version 17 doesn't work? Am I
>>> doing something wrong? Is there any workaround available? Or
>>> should/must I go back to an older version, e.g. MSVC 16?
>> 
>> It means that MSVC v17 is unsupported (ie. untested). The check is
>> made in WindowsArchitecture.msvc_target() in platforms.py. You can try
>> relaxing the check and seeing it fi works.
>> 
>> Phil
>> 
>> -------- Weitergeleitete Nachricht --------
>> 
>> BETREFF:
>> Need support for pyqtdeploy
>> 
>> DATUM:
>> Mon, 18 Nov 2024 17:49:51 +0100
>> 
>> VON:
>> Dr. Wolfgang Schilling <wschill at freenet.de>
>> 
>> AN:
>> info at riverbankcomputing.com
>> 
>> Dear All!
>> 
>> I hope I'm doing the right thing to provide this question to you. If
>> it's not the correct contact, please let me know.
>> 
>> I've a developped a Python/PyQt5 application which I want to deploy to
>> Windows 10 64bit and Linux 32bit. I found your tool "pyqtdeploy" which
>> seems to me the right approach to do so.
>> 
>> I just started with the demo and have problems to get it up and
>> running. I've installed VisualStudio v17, implemented the environment
>> variable "set VisualStudioVersion=17.12.0". In addition I executed the
>> script "vcvarsall.bat amd64_arm64" which ends up with the following
>> message:
>> 
>> All seems fine so far, but when I start your tool with:
>> 
>> python build-demo.py --target win-64
>> 
>> the command stopped with following message:
>> 
>> Does that really mean the latest MSVC version 17 doesn't work? Am I
>> doing something wrong? Is there any workaround available? Or
>> should/must I go back to an older version, e.g. MSVC 16?
>> 
>> Best Regards
>> W. Schilling
>> Germany