-
Notifications
You must be signed in to change notification settings - Fork 11
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
Windows Can't Launch Clay #35
Comments
Hi Silas, thanks for the bug report. It looks like it can't find the libvlc library on your system, could you double check whether it is installed? By the way, are you running it on native Windows or on the Linux Subsystem for Windows (which I would recommend)? As far as I know neither me or @and3rson run Windows as our primary operating system so it is defacto a secondary citizen. If somebody is able to pick up that torch or, at least, regularly test it and report any bugs that they find than that would be really awesome. Anyways, I'll look into this at some point today or tomorrow. |
@ValentijnvdBeek Aha. That helped me get one step closer. For context, I am not using the Linux Subsystem for Windows. Apparently installing VLC is a prerequisite for using Clay, and is not automatically installed with Clay. That got me past the previous error. Now I have a new error message
StackOverflow seems to indicate that this might be an issue with the way the process is being launched. https://stackoverflow.com/questions/25651990/oserror-winerror-193-1-is-not-a-valid-win32-application |
@SilasReinagel Thank you for the report. Can you validate that your VLC matches the architecture of your Python installation? (32/64) I'll try to run clay in VM and reproduce it tomorrow. |
@SilasReinagel I could not reproduce this, but Windows is not supported by urwid lib that we use for TUI so that's another blocker. I maintain urwid and we currently have Windows support on the roadmap, but it won't be coming very soon... Thus Clay will not support Windows anytime soon either. :( |
@and3rson Does it work in the Windows Subsystem for Linux? That might be a better way to support Windows system since it would decrease the maintenance workload on Clay. Personally I feel like it would be a decent trade off since we are not targeting the average user but rather a more advanced level subsystem that prefer commandline[1] applications over GUI applications. [1] In spite of Clay requiring xorg, Qt, and (in the past) GTK+ |
@SilasReinagel @and3rson I just switched the bug for the wontfix tag since it seems to me like this is expected behaviour and that there isn't a lot we can do about it until urwid adds Windows support. I also changed the name to indicate that it applies to all versions of Windows. Do you both agree with this? |
@ValentijnvdBeek That’s unfortunate, but acceptable. Perhaps I will experiment with the Windows Subsystem in the near future. |
Error message:
The text was updated successfully, but these errors were encountered: