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
Build Script for windows #78
Conversation
Adds a build script for windows
Pyinstaller is used to build the windows executable
Thanks to @williamtcastro for pointing it out
So im considering to change --onefile to --onedir because this reduces the start process from 12s to under 2s but the disadvantage to that is that, we have a executable and a directory (and not just 1 file) that have to be in the same parent directory for it to work. |
I changed it to output an executable and a _internals dir because this makes it, atleast from my experience, much faster (12s -> 1-2s). This is probably because the decompression that has to happen before startup if its in one file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its a great optiion to have a faster start but if is possible to run as a option for the user witch it could build either a portable one or a folder structure
So I was able to get it to build the .exe, but it won't launch and I get this error:
I have no "_internal" folder inside the build directory. Is there something I should be doing differently? |
Ah, I needed to launch the .exe in the dist folder, not the build folder... |
Sorry i didn't answer. im currently learning for my A-Levels(or rather the german equivalent) |
Adds a build script for a windows executable
It intentionally doesn't hide the console for the exe because windows defender then complains that it is a malicious programm.
Also i oriented the build script of of the mac os build script from @williamtcastro