On 01/09/2014 12:38 PM, Balestrieri, Francesco wrote:
Thanks Raphael, great work!
-----Original Message-----
From: Crosswalk-dev [mailto:crosswalk-dev-bounces@lists.crosswalk-
project.org] On Behalf Of Raphael Kubo da Costa
Sent: Thursday, January 09, 2014 4:06 PM
To: crosswalk-dev@lists.crosswalk-project.org
Subject: [Crosswalk-dev] Basic support for Tizen IVI and Wayland has landed
I've been working on XWALK-403 for a while now, and today I finally finished
committing the initial set of changes required to make Crosswalk build on Tizen
IVI. Since Tizen IVI uses Wayland instead of X11, this also means an initial
set of
changes required to make Crosswalk build and run on Wayland has also landed
:-)
For Tizen IVI, this means that building Crosswalk using GBS as usual Just Works
(TM), provided you point to an IVI repository instead of a Mobile one in your
gbs.conf. And if you are a Crosswalk developer, it means you need to be more
careful when changing the spec file and make sure whether a new dependency
you want to introduce is available for both Tizen 2 and Tizen 3/IVI. If it
isn't, add
it in the appropriate conditional blocks.
For Wayland, this means it is now possible to run Crosswalk inside Weston. The
work needed to achieve this was close to zero on the Crosswalk side: we simply
stand on the shoulders of the Ozone-Wayland team
(https://github.com/01org/ozone-wayland), who work with the Chromium guys
on their Ozone layer and also on proper Wayland support for Chromium as a
whole. Building Crosswalk with Ozone-Wayland support is a matter of passing
-Duse_ash=0 -Duse_aura=1 -Dchromeos=0 -Duse_ozone=1
to gyp_xwalk (or setting the GYP_DEFINES environment variable accordingly). If
you have more questions about Ozone and/or Wayland, please ask Tiago
Vignatti or Kalyan Kondapally.
So what's next for us in this area. Quite a lot, I'd say:
o We need to set up a build slave in build.crosswalk-project.org that
builds Crosswalk on Tizen-IVI.
o At some point we will start producing canaries for IVI too.
o The Tizen integration we currently have is pretty much all
mobile-specific, including the variable and the define names we use
in gyp and the source code. They are all disabled for IVI, and we
need to check which parts can be shared.
- Some of those things need to be implemented in Ozone-Wayland
itself. For example, there is no "scim" package on IVI, and the IME
integration needs to be done in a lower level than Crosswalk.
I'm sure the Ozone-Wayland guys would love to have more helping hands as
well. If you're interested in Wayland and know one thing or two about graphics,
please ping them.
good stuff Raphael, thanks! We invite everyone to join #ozone-wayland at
freenode to discuss the implementation specific stuff mentioned, among
others.
Tiago
_______________________________________________
Crosswalk-dev mailing list
Crosswalk-dev@lists.crosswalk-project.org
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
