Wayland client support #183
Conversation
In order to effectively use the Wayland platform, you must provide shell integration plugins. Introduce a deployer for these, and a new environment variable, EXTRA_WAYLAND_SHELL_INTEGRATION_PLUGINS to specify them.
In order to use the Wayland QT QPA platform, you must provide: 1) libwayland 2) A shell integration plugin 3) A graphics integration plugin For Raspberry Pi Bookworm users, (1) is straightforward, (2) can rely on the default plugin, and (3) will likely be egl - but this deployer will just package all of them, if you ask for it.
|
Example fragment appimagecraft configuation:
|
|
I'm prepared to withdraw this PR as the functionality already exists in the tree, albeit in a different way than I'd implemented. |
|
Sorry what am I missing that you say that this already exists? |
While this PR would have introduced separate deployers for the Qt plugin directories, there's already a combined deployer in the tree, which can service my requirements for Raspberry Pi Imager. |
|
well that install the Qt compositor libraries as well, not sure it's the best thing |
|
I was just trying to pack a wayland libs again and I think your proposal is better, tho I would instead hook both shell and graphics integration into a single WaylandClient, it's easier and better to exclude-libraries than picking what we might need. |
With these commits, and a suitable AppImageCraft configuration, I can package Raspberry Pi Imager with the Wayland QPA platform and avoid the use of Xserver on Raspberry Pi OS Bookworm (and likely other clients too).
Fixes: #160 and #130.