About Chromium on Wayland and GDP
OAndreasson at luxoft.com
Mon Nov 6 04:47:15 EST 2017
I got a little bit curious about the status and did some tests last week with the latest gdp
feature_sdl_pyro branch (includes feature_chromium branch), built for rpi3, it seems to work like a
charm for me.
This should also mean it works for rpi2 according to my discussions with Gunnar (rpi3 build
apparently builds 32bit for now, while the hardware is 64bit capable.... ie, when switching rpi3
builds to 64 bit, it might be an issue, but I don't see it as a problem until we run into it).
I hope I'm not too late to save you some time :).
On Tue, 2017-10-31 at 17:51 +0100, Jacobo Aragunde Pérez wrote:
> Hi Gunnar,
> find my answers inline.
> On 31/10/17 16:54, Gunnar Andersson wrote:
> > Hi Jacobo, (+ projects)
> > I saw this in the EG-NW minutes for last week.
> > > Jacobo Aragunde reported that the Chromium project is now aming to
> > > support Wayland compositing natively. Details will be discussed during
> > > the upcoming Chromium Developers Conference. The Chromium developers
> > > have agreed to develop an upstream plan for the submissions made
> > > by Igalia.
> Actually, details were discussed in the BlinkOn and Web Engines
> Hackfest. These events have already happened, sorry if I wasn't clear
> about that. My colleagues will start splitting and sending their
> contributions for review, and Googlers have made sure they will have
> time to review them.
> I will update the minutes.
> > > Jacobo Aragunde is currently testing the latest changes on GDP.
> > (and similar this week).
> > First, this is cool.
> > Second, please keep in touch. I want to make sure you are not getting stuck
> > on any general GDP issues that the team could resolve for you.
> Sure, I will update you weekly, at least, and report any issues in Jira.
> > By the way, let's review the status. GDP still supports only some platforms
> > for Chromium:
> > - R-Car (M3 starter kit tested)
> > - Minnowboard
> > Dragonboard: We still have a working build, but not tested for Dragonboard
> > because the GDP team have lacked hardware (a while back we fried one of the
> > boards).
> > - qemux86-64: This worked quite well in QEMU last time I tested, so I think
> > we'll just shift QEMU to include Chromium in the future.
> > Then, for R-Pi 2 and 3, maybe you know if there has been some progress
> > outside of GDP? Maybe we're actually pretty close and just need some
> > adjustment? (that the GDP team could test independent of you)
> I will build an image to check the status again. I'm pretty sure the
> chromium and chromium-wayland packages provided in meta-browser have
> been used successfully ran on these boards before, so I need to check
> what's the problem with GDP.
> > As I've said before, we're probably down-prioritizing graphical development,
> > and hence Chromium, a little bit, but that doesn't mean it's down to zero
> > (and we'll definitely take any contribution!)
> > Only, it would help a lot from maintenance point of view if we could align
> > GDP back into a single Master branch again - and to do that we want to
> > support the building all targets from that single branch, so that's why it's
> > still important to close the gap on the remaining platforms.
> > Main feature branches right now are:
> > - feature_chromium_pyro (not really kept up to date last month since we're
> > preferring the SDL branch)
> > - feature_sdl_pyro (Same as Chromium feature + SmartDeviceLink. SDL has an
> > HTML interface, so it needs Chromium - therefore this one basically
> > supersedes the chromium feature branch)
> > - master (no Chromium or SDL)
> I will use the feature_sdl_pyro branch to check Chromium on RPi.
> > Actually feature_sdl_pyro is missing the following commit, so that is one
> > that I'm not sure if we have properly tested:
> > 5dc47df Gunnar Andersson (5 weeks ago) chromium-wayland: Depend on
> > wayland-ivi-extension
> > https://github.com/GENIVI/genivi-dev-platform/commit/5dc47df
> > The change seems right to me, but the build error we had before that was
> > intermittent.
> That should fix the issue, thanks for pointing it out. The fact that it
> was intermittent confirms it was a package dependency problem; it only
> failed if wayland-ivi-extension didn't happen to get built earlier than
> Chromium (which usually does, because it's a much smaller package, and
> that's why I hadn't found it).
> As I said before, I will keep you updated!
Lead Software Engineer
Östrahamngatan 16, Gothenburg, Sweden
oscar.andreasson at pelagicore.com
PELAGICORE a part of LUXOFT
Registered Office Gothenburg, Sweden
Registration No. 556780-4199
This e-mail and any attachment(s) are intended only for the recipient(s) named above and others who have been specifically authorized to receive them. They may contain confidential information. If you are not the intended recipient, please do not read this email or its attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and then delete this e-mail and any attachment(s) or copies thereof from your system. Thank you.
More information about the genivi-projects