-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable use of pyinstaller #14
Comments
Getting the CPython interpreter to work on Wine is not trivial at all, unfortunately. The installers from
If you could share a complete, reproducible example (configuration / list of steps), I could look deeper into it. |
https://gist.github.com/schlomo/7f3c65969ca06f384e85accb8c88bff4 is a test case that demonstrates the problem with the help of a little
(showing only the relevant bits of the So what happens is that Running the resulting file on Windows doesn't help either. |
Opened pyinstaller/pyinstaller#5198 for cross-reference |
One small mistake that immediately sticks out: You're testing the build with the command
I just tested the procedure (wine64 / win64). This is how far I get:
Looks like an encoding issue. This can probably fixed with a Wine setting if I had to guess. I look deeper into it in next couple of days. |
Ok, just a guess - this appears to work: wenv pyinstaller --onefile "c:/python-3.8.4/Lib/site-packages/yamlreader/yamlreader.py" This is the actual entry point of |
Ok, still can not launch in Wine 5.17. Root cause is a Wine bug. Binary could actually be ok ... |
Maybe https://github.com/spesmilo/electrum/blob/aae06116f9cff9e3540c20a8fb6e51011ca9b3ab/contrib/build-wine/prepare-wine.sh is an interesting way how to install a full featured Python from MSI instead of using the embedded distribution? |
|
@s-m-e I checked and found out that Besides that I think that testing the resulting EXE in a clean wine environment is better / more correct than testing it in the build environment as that ensures that the resulting binary works without the build environment. Wrong thought? |
There is nothing wrong with that, sure. However, I am not changing the configuration of the wine environment that I create for
If you want to test your EXE, you may need to apply the patch mentioned in this ticket and build Wine from sources. I attached my Wine-based built of yamlreader. Looks OK but does does not launch due this exact Wine bug. You should probably see the same thing.
Also interesting. AFAIK this depends on how Wine is packaged, which differs between distributions and releases. On openSUSE for instance, |
This is a really amazing tool!
Could you enable the use of pyinstaller? The use case is creating a Windows EXE self-contained file from a Python tool and thereby foregoing the need for a Windows build machine.
I got it all to work but then pyinstaller runs into this problem:
I was able to proceed after copying that file from the Python 3.8.4 sources but then I got stuck with this error:
Any ideas how to get pyinstaller to work in wenv? That would really help me a lot.
The text was updated successfully, but these errors were encountered: