PyInstaller
Failed to load Python DLL - seems something's going wrong during the build process #8656
-
|
I created a little Systray App (HueConnect) in Python. The script runs fine from the command line. When building in onedir-mode, the build process with PyInstaller runs successfully (no errors shown and process completed successfully). When starting the application from /build/HueConnect, a popup error is shown and the application does not start up:
I checked Analysis-00.toc and EXE-00.toc and both contain references for the related python311.dll pointing to the correct location:
Interestingly in the error message the path to python311.dll is different: While J:\hueconnect\build\HueConnect exists, there is no "_internal" directory below that path. After creating the "_internal" directory manually, copying python311.dll to it and trying to start the application again, a different Error pops up:
Here I'm stuck: Obv. something with embedding the pyhton interpreter and needed runtime libs did not work while building the EXE with pyinstaller. However, there is no errors issued when building the EXE: _J:\hueconnect>pyinstaller --onedir --clean --name HueConnect --add-data "hueconnect.conf;." --add-binary "icon_default.jpg;." --noconsole --noconfirm .\HueConnect.py Does anyone has an idea would could have gone wrong/what i might have missded? Any idea/hint is very welcome. Thanks a lot! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 9 replies
-
You seem to be running .exe in the |
Beta Was this translation helpful? Give feedback.
-
|
Update: It's a windows file lock from a backup process that just started. I forgot it's running right now. However, as it just started, it think it's unrelated to the intial problem. I will end the process and go on with the --nosonsole approach. -- Now that's interesting: With J:\hueconnect>pyinstaller --onedir --clean --name HueConnect --add-data "hueconnect.conf;." --add-binary "icon_default.jpg;." --noconsole --noconfirm --debug bootloader .\HueConnect.py During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Beta Was this translation helpful? Give feedback.
-
|
My first guess would actually be that your windowed/noconsole appliation is running in the background, and that's why you cannot remove its contents. Look at the system tray (since you say it's a systray app), or open Task Manager and find the running process. |
Beta Was this translation helpful? Give feedback.
-
|
The systray and the task manager were the first things i checked :-) There was no related process. |
Beta Was this translation helpful? Give feedback.
-
|
Well, as I wrote earlier, just adding |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I understood, you're directions were very clear. I just followed your advice (recompiling without --noconsole) and i got an error message from my application on the console - it can't resolve the relative path to the config file. My bad :-( So PyInstaller was working perfectly! Thanks a lot Rok for your fast, friendly and professional support. I'm a bit embarrassed i didn't think of removing --noconsole myself - noob mistake :-) -- |
Beta Was this translation helpful? Give feedback.
Well, as I wrote earlier, just adding
--debugwon't do anything, because you are also using--noconsole(which I missed initially). So you'll have to also remove--noconsoleif you want any console output at all.