You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the "Initializing ..." message on startup (#50) is written directly into the Pyinstaller bootloader (due to the Splash Screen feature not being currently being supported on macOS):
// If only one temp dir is found then we can assume that we're in the parent // and should output the "Initializing ..." messageif (count==1) {
printf("Initializing ...\n");
}
The issue with the current logic is that if more than one DRS Downloader process is started, only the first process will output the startup message.
A more robust approach might be to update Pyinstaller to create a temporary "parent" directory for each new intitial process in which subsequent calls to the bootloader can extract files into (each multiprocessing Python process calls the same bootloader on startup).
Could leverage the runtime_tmpdir arguments in the EXE class of Pyinstaller:
Currently the "Initializing ..." message on startup (#50) is written directly into the Pyinstaller bootloader (due to the Splash Screen feature not being currently being supported on macOS):
bootloader/src/pyi_main.c
The issue with the current logic is that if more than one DRS Downloader process is started, only the first process will output the startup message.
A more robust approach might be to update Pyinstaller to create a temporary "parent" directory for each new intitial process in which subsequent calls to the bootloader can extract files into (each multiprocessing Python process calls the same bootloader on startup).
Could leverage the
runtime_tmpdir
arguments in the EXE class of Pyinstaller:PyInstaller/building/api.py
Which is then passed to the function responsible for making the temp directory to unpack the archive:
bootloader/src/pyi_archive.c
The text was updated successfully, but these errors were encountered: