added waylandcompositor plugin deployer #157
Conversation
|
@TheAssassin any chance on getting this merged? |
|
Sorry, totally missed your PR. Too much other things to worry about. I'll have a look. |
|
Is there any reason you need to deploy this manually other than the fact that the plugin still prefers X11 (which causes less of a headache)? I mean, it's fine the way it is, just curious. |
|
Thank you! I'd appreciate a reply nevertheless. |
|
Sorry for the late reply. I simply wanted my app to work with wayland as well. There was no special reason other than I had nothing to do at work :D |
|
@SushiTee I think the main question is whether there a reason to not ship these plugins? Likely everybody would like their app to work with Wayland as well, so unless there are reasons not to support this, shipping the necessary plugins should potentially be an opt-out instead of an opt-in. |
|
True. In my case the app just works with both. On systems without wayland support or where it is simply not the default the app starts using XCB without problems. |
Found the information in linuxdeploy#157
Found the information in linuxdeploy#157
Found the information in linuxdeploy#157
Found the information in #157
I added a class to deploy the following 3 plugin directories:
when the plugin waylandcompositor is selected.
I confirmed my specific app working with wayland like this. Here are the environment variables I set: