View Single Post
xerxes2's Avatar
Posts: 513 | Thanked: 651 times | Joined on Feb 2011 @ Sweden
#406
Originally Posted by MartinK View Post
I think GTK3 should be good to go as it should have mainline Wayland support. I would say some mucking with GTK3 packages from Fedora/OpenSuse in Mer OBS should do the job.

GTK2 is more complicated as it does not support Wayland, so XWayland will be needed first for it to work. Hacking it work directly with Wayland might not be an option, as at least GDK is directly using & exposing (I've actually used some of that in modRana ) a lot of X stuff.

Still, GTK is IMHO not that suitable for mobile GUI development. Sure, it is possible, but it is quite a masochistic exercise, provided there are better suited alternatives available, such as Qt.
I got a bit curious about this so I tried to get GTK to work in Sailfish. Long story short, after upgrading and building the stack (glib, atk, gdk-pixbuf, cairo, pango, fontconfig, harfbuzz, wayland) under GTK which is needed for the newest GTK version (3.11.0), I finally got GTK to start compiling ... but then I hit this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=710584

So once that bug is fixed GTK can be built on Sailfish. I'm not sure if the Sailfish compositor allows it to run though. But if it does I guess that GTK3 apps will at least run on Sailfish. GTK2 needs xwayland to run and that is another story ...
__________________
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
 

The Following 5 Users Say Thank You to xerxes2 For This Useful Post: