[PATCH weston] README: introduce libweston
ppaalanen at gmail.com
Fri Jul 17 00:04:30 PDT 2015
On Thu, 16 Jul 2015 18:56:20 -0700
Bryce Harrington <bryce at osg.samsung.com> wrote:
> On Thu, Jul 16, 2015 at 11:55:03AM +0300, Pekka Paalanen wrote:
> > A quick fix would be to have a runtime switch in toytoolkit to ask for
> > cairo-egl, and default to cairo-image. This way we'd limit the
> > cairo-egl impact to just the demos that actually ask for it.
> > A more involved fix would be to get rid of cairo-egl completely, and
> > remove the support from toytoolkit. Then demos that depended on it
> > would need to get their decorations drawn with cairo-image, copied into
> > textures, and blitted in GL to the surface.
> Mind if we postpone eliminating this functionality for a few months?
> I'd like to do some experimentation with cairo performance under wayland
> and I'd like to quantify the benefit/cost of cairo-egl before we chuck
Sure, I have no time planned for doing any of that so far. And if we
only did the quick fix, it wouldn't hinder you at all.
Would be quite interesting to see actual measurements of start-up time,
memory usage (RAM + VRAM), and of course rendering performance itself.
I suppose there was a good reason to implement renderer switching in
the DRM-backend to speed up Weston's own start-up, which implies that
in some cases initing EGL and GL may take a while. Or maybe that was
just an experiment, as it was left at a debug key binding level AFAIK.
One should be able to start Weston on DRM with Pixman renderer and hit
the key to switch to GL.
More information about the wayland-devel