Rok Mandeljc
Rok Mandeljc
This is indeed a bold move (especially for the first contribution), but the situation with shared libraries in PyInstaller is rather complicated... --- > So basically, most dynamic modules are...
> The "libs" is hard coded here. Is there anyway in the python bootloader part to fetch EXE OPTIONS? like the pyi_arch_get_option() rom the binary bootloader? Else the pyi-lib-subdir has...
What if we saved the temporary executable without any suffix?
Also, it seems that in onefile builds, we end up with `name.exe.notanexecutable` instead of `name.notanexecutable`...
The QtWebEngine problem on macOS is a bit more specific; we should not be breaking up the .framework bundle as this breaks the QtWebEngineProcess helper, and is the reason why...
No, it should be possible with sufficient amount of file relocation and symlinking to get around the dot-in-name problem; at least according to the feedback we got from users who...
FWIW, I don't think this issue is related to M1; the linked build fails to run on my test x86_64 systems, too, with the same error. And it looks like...
I don't think SDL libraries were collected into this new build...
Hmm, I suspect it might be easier to just collect the `libmpg123.0.dylib` from homebrew in addition to all libraries that were already collected than to switch to `pysdl2-dll`. From target...
I kind of doubt people who are familiar with PyInstaller and its warning verbosity are going to notice those deprecation warnings either... especially for builds that are done on the...