{"id":7,"date":"2016-05-18T20:21:30","date_gmt":"2016-05-18T20:21:30","guid":{"rendered":"http:\/\/blogs.igalia.com\/tonikitoo\/?p=7"},"modified":"2016-05-20T15:09:51","modified_gmt":"2016-05-20T15:09:51","slug":"chromium-content_shell-running-on-wayland-desktop-weston-compositor","status":"publish","type":"post","link":"https:\/\/blogs.igalia.com\/tonikitoo\/2016\/05\/18\/chromium-content_shell-running-on-wayland-desktop-weston-compositor\/","title":{"rendered":"[Chromium] content_shell running on Wayland desktop (Weston Compositor)"},"content":{"rendered":"

During\u00a0my first weeks\u00a0at Igalia, I got an interesting and promising task of Understand the status of Wayland support in Chromium upstream<\/strong>.<\/p>\n

At first I could\u00a0see clear signs that Wayland<\/a> is being actively considered by the Chromium community:<\/p>\n

    \n
  1. Ozone\/Wayland project<\/a> by Intel – which was my starting point as described later on.<\/li>\n
  2. The\u00a0meta\u00a0bug “upstream wayland backend for ozone (20% project)<\/a>“, which has some recent activity by the Chromium community.<\/li>\n
  3. This comment in the chromium-dev mailing list<\/a>\u00a0(by a Googler):<\/li>\n
  4. \n

    “(..) I ‘d recommend using ToT. Wayland support is a work-in-progress\u00a0and newer trees will probably be better.”.<\/p><\/blockquote>\n

    Chromium’s DEPS<\/a> file has “wayland” as one its\u00a0core dependency (search for “wayland”).<\/li>\n<\/ol>\n

    Next step, naturally, was get my hands dirty, compiling and experimenting with it. I decided to start with content_shell<\/a>.<\/p>\n

    \n

    Environment<\/strong>:<\/p>\n

    Ubuntu 16.04 LTS, regular Gnome session (with X) and Weston Wayland compositor running (no ‘xwayland’\u00a0installed) to run Wayland apps.<\/p>\n

    GYP_DEFINES<\/strong><\/p>\n

    component=static_library use_ash=1 use_aura=1 chromeos=0<\/strong> use_ozone=1 ozone_platform_wayland=1 use_wayland_egl=1 ozone_auto_platforms=0 use_xkbcommon=1 clang=0 use_sysroot=0 linux_use_bundled_gold=0<\/em><\/p>\n

    (note: GYP was used for personal familiarity with it, but GN applies fine here).<\/p>\n

    Chromium version<\/strong><\/p>\n

    Base SHA 5da650481 (as of 2016\/May\/17)<\/p>\n

    Initial results<\/strong><\/p>\n

    As is, content_shell\u00a0built fine, but hung\u00a0at runtime upon launch, hitting a CHECK at desktop_factory_ozone.cc(21).<\/p>\n

    Analysis and Action<\/strong><\/p>\n

    After\u00a0understanding current Ozone<\/a>\/Wayland upstream support,\u00a0compare designs\/code against 01.org<\/a>,\u00a0I could start\u00a0connecting some of the missing dots.<\/p>\n

    The following files were “ported” from 01.org:<\/p>\n