Need help with ozone-wayland?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

201 Stars 81 Forks Other 1.0K Commits 44 Opened issues


Wayland implementation for Chromium Ozone classes

Services available


Need anything else?

Contributors list


Ozone-Wayland is the implementation of Chromium's Ozone for supporting Wayland graphics system. Different projects based on Chromium/Blink like the Chrome Browser, Chrome OS, Crosswalk, among others can be enabled now using Wayland.

Alt text



Ozone-Wayland architecture can be found here.


We use Ubuntu 14.04 LTS (Trusty Tahr), 32/64-bit but a kernel from Raring though. One can install it pretty easily just

sudo apt-get install linux-generic-lts-raring
. This version is needed for using Mesa master 9.3.0-devel, a requirement for Weston. Besides, make sure you have at least 25 GB of disk space to store all the sources and a few targets to be compiled (with debugging symbols).

Firstly you'd need to set up the Wayland libraries (version >= 1.4.0), and the Weston reference compositor that you will be running Chromium onto. The information on Wayland's web page should be enough for doing so:

Please note that at the moment support for Wayland's XDG Shell protocol only works with the 1.6 series.

Make sure everything is alright now, setting up the environment variable

and playing a bit with the Wayland clients, connecting them on Weston.

Then you'd need some distribution tools and development packages :

  $ sudo apt-get install gperf libnss3-dev libpulse-dev libdbus-1-dev libexif-dev libpci-dev libpango1.0-dev libelf-dev libcap-dev libasound2-dev libssl-dev libcups2-dev libgconf2-dev libgnome-keyring-dev

If you are running a 64-bit Ubuntu distribution, you'd additionally need :

  $ sudo apt-get install ia32-libs

Then on Chromium's side, we need to setup Chromium's tree together with the Ozone-Wayland implementation. For that you need to use gclient to clone Ozone-Wayland; but first you need to download depot_tools and configure it. Say your Chromium top-level will be in

, you will need:
  $ mkdir -p ~git/chromium
  $ cd ~git/chromium
  $ git clone
  $ export PATH=`pwd`/depot_tools:"$PATH"

We support HWA Video Decoding using Libva and VAAPI. To enable the support one needs to build and install these packages. Note: This is still work in progress. You can skip these dependencies if you don’t need this support.

One needs to set the installation prefix $WLD(Below) to be same as the one used for setting up Wayland environment.

  $ git clone git://
  $ cd libva/
  $ git checkout libva-1.5.0
  $ ./ --prefix=$WLD
  $ make -j4 && make install
  $ git clone git://
  $ cd intel-driver/
  $ git checkout 1.5.0
  $ ./ --prefix=$WLD
  $ make -j4 && make install
now we can clone Ozone-Wayland and fetch all the dependencies of it, including Chromium itself:
  $ gclient config ssh://[email protected]/01org/ozone-wayland.git --name=src/ozone --deps-file ".DEPS.git"
  $ gclient sync 
  $ export GYP_DEFINES='clang=0 use_sysroot=0 component=static_library linux_use_bundled_gold=0 use_ozone=1 ozone_auto_platforms=1 ozone_platform_wayland=1 use_xkbcommon=1' 

If you want to enable HWA Video Decoding, you need to have the following GYPDEFINES: ``` $ export GYPDEFINES='clang=0 usesysroot=0 component=staticlibrary linuxusebundledgold=0 useozone=1 ozoneautoplatforms=1 ozoneplatformwayland=1 usexkbcommon=1 proprietarycodecs=1 ffmpeg_branding=Chrome' ```

It may take a considerable time for downloading the trees. If everything went fine, now we're able to build.

For now, also apply some patches:


TIP: to speed up debug builds you can disable Blink debugging symbols by setting removewebcoredebugsymbols=1 in GYPDEFINES.

Note that in Chromium, gyp uses pkg-config for checking where are Wayland libraries on the system, so double check that you are not mixing some that was already there with latest that you just got and compiled from git.

TIP: if you followed Wayland's web page instructions, then you probably want to set the

variable as
and add it in your .bashrc to be as default.

Now we can conclude compiling a few targets like Content Shell (content_shell) or the Chromium browser:

  $ cd src/
  $ ./build/gyp_chromium
  $ ninja -C out/Debug -j16 chrome

(if you get any build errors, please execute "git log" and verify that the first "commit" line matches the "chromium_rev" one found in

. If it doesn't, run "git checkout $ID", apply the patches and compile again)

That's all. At this point you should be able to connect Chromium on Weston using:

  $ ~/git/weston/src/weston &
  $ ./out/Debug/chrome --no-sandbox --ignore-gpu-blacklist


If you want to enable Sandboxing provided by Chromium, please follow the instructions from here:

Working with Ozone-Wayland Release branch:

Instructions can be found here:


We pin chromium to a particular revision in order to keep upstream changes from breaking our build. Updating that revision to a newer one and fixing any resulting breakage is called gardening. To sync a different version of chromium, update chromium_rev in .DEPS.git to a newer revision then run the gclient sync again. Fix any build errors, and commit both changes.


Instructions can be found here:


Ozone-Wayland's code uses the BSD license (check the LICENSE file in the project).


Build Wayland & Weston

If you want to build and run ozone-wayland, you should install wayland and weston first. Here is the instruction using jhbuild.

Install jhbuild

Please refer to this instruction:

Install dependent packages using apt-get

$ cd ~/chromium/src
$ ozone/tools/jhbuild/install-dependencies

Build and install Wayland & Weston

$ cd ozone/tools/jhbuild
$ jhbuild -f wayland.jhbuildrc

Run Weston

$ jhbuild -f wayland.jhbuildrc shell
$ cd ~/chromium/src
$ out/wayland/root/bin/weston --fullscreen

Run ozone-wayland in Weston

Open a weston terminal

$ out/Release/chrome --no-sandbox

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.