-
Notifications
You must be signed in to change notification settings - Fork 667
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
RuntimeError: Could not import backend "Glfw": #442
Comments
👋 Hi, just a reminder that if you haven't read the help post yet, give it a read to see if your issue is covered in it and make sure to follow the debugging section. Also please note, as stated in the README, if your issue is only associated with your application and not auto-py-to-exe itself, please do not create an issue in this repository - instead, comment on the help post, video or create a new discussion. |
This looks like a classic case of PyInstaller not detecting a "hidden" import. Potentially this could be fixed by adding "glfw" to "--hidden-import" in the advanced section. |
already did that as I said in the post!!
|
My bad, I didn't see any reproduction steps so had assumed you didn't try that. Could you provide the "Current Command" generated at the bottom of the UI before you package and the build output. Also when you package it into one directory, are you able to see the glfw library inside the folder? Should be with the other external dependency folders. |
Sorry for no putting the steps, my bad there!
Of course I can show it, here it is:
Actually no, idk why but all the other dependencies are there except glfw, I have it installed and in my environment variables so it's kinda weird |
Hmm, that's odd. Could you run this in PowerShell and make sure glfw is in this list,
Could you also try adding "glfw" to --collect-all in the advanced tab - this will pick up binaries missing but the fact this library isn't showing up in the exe hints this might not fix it. Also this isn't an auto-py-to-exe issue directly btw, this issue lies around PyInstaller (but isn't PyInstaller's fault - more around how the libraries are setup). Still happy to offer my knowledge around the subject though! |
it worked! thank you! |
I'm trying to package a script that has the p5.py library, it runs normally in vs code and I have all the dependencies installed, yet when I try to run the executable it always gives me an error related to the GLFW library, I've already tried to put it in the hidden imports section and it gives me this message :
Here is all the libraries I have in the script:
Your Environment:
Here is all my librabries
The text was updated successfully, but these errors were encountered: