-
Notifications
You must be signed in to change notification settings - Fork 6
Standalone wheel #92
Comments
I forgot to write in that thread that I'm guessing that the files which should be copied there are in fact not properly copied, perhaps similarly as in #44. This (standalone wheels) is what everyone wants and it would be pure gold to have. Unfortunately, I don't have the time available for such a task. |
By the way, if you're on Windows you can check this out: #69 |
Thanks! That accomplished what I was trying to do on Windows. |
How is that different from standalone? |
What do you mean? To me, it doesn't seem properly configured to be standalone even if it bundles a lot of the right stuff. I'm not sure it has everything bundled although it clearly has a lot more than the Linux/macOS wheels. |
I don't know what might still be missing, but for me, setting the QT_QPA_PLATFORM_PLUGIN_PATH to the platforms folder under site-packages seems to work as well as setting it to C:\Qt\Qt5.6.2\5.6\msvc2015_64\plugins\platforms. And not setting it at all results in the error you referenced in #69, so it doesn't appear to be getting Qt libraries from anywhere else, and I don't have anything in any other environment variables pointing to anything for Qt. I don't know if there are features I'm not using or something, but I haven't run into anything yet. |
It's possible that everything is properly bundled with the Windows wheel and that some configuration is missing to tell PySide2 where to find the DLL files. I found out about the However, on Unix, wheels doesn't have any of the required Qt libraries bundled. |
Please see then new repositories for standalone wheels: |
Interested in seeing if there's an chance of getting standalone versions of the wheels. @leycec mentioned a --standalone option for setup.py in #44, don't know if that might be useful.
The text was updated successfully, but these errors were encountered: