Ozone-Wayland is the implementation of Chromium's Ozone for supporting Wayland graphics system. Different projects based on Chromium/Blink like the Chrome browser, ChromeOS, among others can be enabled now using Wayland.
- Design - the architecture behind
- Howto - set up the system environment, build and run
- Contributing - help develop and send patches
- License
Ozone is a set of classes in Chromium for abstracting different window systems on Linux. It provides abstraction for the construction of accelerated surfaces underlying Aura UI framework, input devices assignment and event handling.
http://www.chromium.org/developers/design-documents/ozone
Before when using Aura on Linux, all the native windowing system code (X11) was spread throughout Chromium tree. Now the idea is that Ozone will abstract the native code and because it's a set of class factories, it will switch for whoever is the window system. The biggest advantage of this API is that it allows to implement the needed window system bits externally from the Chromium tree, which is great because it is where the loaded work situates.
Worth to mention also that when Aura is used, there's no need for graphics toolkits, such as GTK+, EFL etc.
We use Ubuntu 12.04 LTS (Precise Pangolin), 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.
Firstly you'd need to set up the Wayland libraries (version >= 1.2.9), 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:
http://wayland.freedesktop.org/building.html
Make sure everything is alright now, setting up the environment variable $XDG_RUNTIME_DIR and playing a bit with the Wayland clients, connecting them on Weston.
Then on Chromium's side, we need to setup Chromium's tree together with the Ozone-Wayland implementation "aside" of it. For that you have to use a special .gclient configuration that clones both of the trees (see next section); but first you need to download depot_tools and configure it. Say your depot_tools live in ~/git/chromium/depot_tools and your chromium top-level directory is in ~/git/chromium/src, you will need to jump to ~/git/chromium and run:
$ gclient sync
It may take a considerable time for downloading the trees, but once that is done, the .gclient will automatically switch the chromium repository to "master-ozone" branch and apply a few patches on top of it (not everything is upstream yet). If everything went fine, now we're able to generate the needed building files:
$ cd src/
$ export GYP_DEFINES='component=static_library use_ash=0 use_aura=1 chromeos=0 use_ozone=1'
$ ./build/gyp_chromium
TIP: to speed up debug builds you can disable Blink debugging symbols by setting remove_webcore_debug_symbols=1 in GYP_DEFINES.
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 PKG_CONFIG_PATH variable as $HOME/install and add it in your .bashrc to be as default.
Now we can conclude compiling Content Shell target.
$ ninja -C out/Debug -j16 content_shell
That's all. At this point you should be able to connect content_shell on Weston using:
$ ~/git/weston/src/weston &
$ ./out/Debug/content_shell --no-sandbox
solutions = [
{
u'managed': True,
"name": "src",
u'url': u'https://chromium.googlesource.com/chromium/src.git',
u'custom_deps': {},
u'deps_file': u'.DEPS.git',
u'safesync_url': u'',
u'custom_vars': {u'webkit_rev': u''},
# this suppresses the execution of the gyp action from src/DEPS by setting
# the action to nothing.
# TODO: rjkroege recommended but in fact I'm not sure this is needed.
"custom_hooks": [ {"name": "gyp"} ]
},
{
# note that if you try another method for cloning below (like using https
# instead ssh), then you will want to change it also in gclient/DEPS
"name" : "src-ozone",
"url" : "ssh://git@github.com/01org/ozone-wayland.git",
"deps_file": "gclient/DEPS"
}
]
hooks = [
{
# this will apply the needed patches in Chromium tree. It pretty much
# generates the Wayland dependencies on .gyp files there and also patch
# other small changes. Ideally this shouldn't exist and Ozone-Wayland would
# be just dynamically loaded within Ozone there.
"name": "gyp",
"pattern": ".",
"action": [
"bash", "src/ozone/patches/patch-chromium.sh"
]
}
]Instructions can be found here: https://github.com/otcshare/ozone-wayland/wiki
Ozone-Wayland's code uses the BSD license (check the LICENSE file in the project).