https://bugs.documentfoundation.org/show_bug.cgi?id=167571
--- Comment #4 from Klaus Kusche <[email protected]> --- I accept your arguments against dlopen, thanks for all the explanations. Thinking about it again, I believe it's mostly gtk's fault, because gtk's API differs when it is built without wayland support. It would be better if gtk provided exactly the same calling interface for a wayland and a non-wayland build, and in the non-wayland case just replaced the wayland-specific functions with dummy implementations returning some error or null value. After all, these functions need to return an error anyway if no wayland is present at runtime. The qt6 base lib also has wayland and non-wayland builds, but as far as I know, both export exactly the same API. The problem is not that I have to build gtk itself with wayland support, the problem is that gtk with wayland pulls in all the wayland dependencies and requires mesa to be built with wayland, most likely for the same linking reasons you described above. > Again, it's a gentoo maintainer decision whether to provide a USE flag. That's what I would prefer and wanted (https://bugs.gentoo.org/960475), but they don't. > This is already the case with skia/qt as far as I am aware. Already tried both, both don't require wayland. skia is very small and fast, but does not respect theme settings at all and hence looks very alien. Qt is much larger, also larger than gtk, looks beautiful, and does respect my gtk theme. It only still has a little bug w.r.t. scrollbars (bug 165466), but qt6 would be an alternative. -- You are receiving this mail because: You are the assignee for the bug.
