Apr-02-2024, 11:21 AM
Hello everyone,
I'm currently working on a project that heavily relies on the scikit-image package. I have an up-to-date Anaconda installation on a Windows 10 64-bit system. My project is developed and tested using Spider IDE. For exporting the script as an executable, I'm using PyInstaller with the following command:
pyinstaller --onedir --distpath=C:\Users\xxx C:\Users\xxx\myscript.py
While this process works smoothly for target Windows machines with 64-bit architecture, things do become complicated with 32-bit systems.
Here's a breakdown of what I've tried:
Initially, I created a separate Windows account and installed a 32-bit Python 3.10.0. However, when attempting to install the scikit-image package via pip, I encountered the error:
...
Need python for x86_64, but found x86. Run-time dependency python found: NO (tried sysconfig)
Virtual Machine Approach:
My second approach involved installing an older version of Python (3.6.7) on a virtual 32-bit Windows 7 machine (Service Pack 1).
Here, PyInstaller appeared to compile the script without errors. However, while running the executable on Windows 10,
I encountered the following error:
Exception in Tkinter callback
Traceback (most recent call last):
File "tkinter\__init__.py", line 1705, in __call__
File "skimage\io\_io.py", line 48, in imread
...
ValueError: Could not find a backend to open
Additionally, trying to run the executable on a virtual Windows XP image resulted in the error message:
The procedure entry point GetFinalPathNameByHandleW could not be located in the dynamic link library KERNEL32.dll
Considering these problems, I'm uncertain if there's a viable method to export an executable compatible with older 32-bit Windows machines. Any insights or alternative approaches would be greatly appreciated.
Thank you for your time.
I'm currently working on a project that heavily relies on the scikit-image package. I have an up-to-date Anaconda installation on a Windows 10 64-bit system. My project is developed and tested using Spider IDE. For exporting the script as an executable, I'm using PyInstaller with the following command:
pyinstaller --onedir --distpath=C:\Users\xxx C:\Users\xxx\myscript.py
While this process works smoothly for target Windows machines with 64-bit architecture, things do become complicated with 32-bit systems.
Here's a breakdown of what I've tried:
Initially, I created a separate Windows account and installed a 32-bit Python 3.10.0. However, when attempting to install the scikit-image package via pip, I encountered the error:
...
Need python for x86_64, but found x86. Run-time dependency python found: NO (tried sysconfig)
Virtual Machine Approach:
My second approach involved installing an older version of Python (3.6.7) on a virtual 32-bit Windows 7 machine (Service Pack 1).
Here, PyInstaller appeared to compile the script without errors. However, while running the executable on Windows 10,
I encountered the following error:
Exception in Tkinter callback
Traceback (most recent call last):
File "tkinter\__init__.py", line 1705, in __call__
File "skimage\io\_io.py", line 48, in imread
...
ValueError: Could not find a backend to open
C:/Users/xxx.png with iomode ri.Additionally, trying to run the executable on a virtual Windows XP image resulted in the error message:
The procedure entry point GetFinalPathNameByHandleW could not be located in the dynamic link library KERNEL32.dll
Considering these problems, I'm uncertain if there's a viable method to export an executable compatible with older 32-bit Windows machines. Any insights or alternative approaches would be greatly appreciated.
Thank you for your time.