On Fri, May 31, 2013 at 10:52:07AM +0100, Burton, Ross wrote:
> On 31 May 2013 10:30, Burton, Ross <[email protected]> wrote:
> >> At the time of writing that weston didn't support runtime detection or 
> >> config files entries for selecting the backend, only commandline 
> >> arguments. So whatever is getting picked at build time, you're stuck with 
> >> that. Does 1.1.x address that situation?
> >
> > Sadly, not as far as I'm aware.  I have 1.1 in another branch but it
> > totally broke GTK+ 3 applications (which didn't repaint after the
> > initial creation), which is pretty sad.  Relevant developers harassed.
> 
> In a massive shock, the weston man page is actually useful.  Sadly
> it's clear that the backend choice is either x11 if DISPLAY is set,
> wayland-over-wayland if WAYLAND_DISPLAY is set, otherwise the command
> line argument finally falling back to the "default" (drm out of the
> box).
> 
> So if we want a single binary that supports both DRM and fbdev, then
> we need to use command-line options.   I guess our startup script
> should handle this and we can add another optional machine-specific
> config file.

Is x11 backend working for you (e.g. in qemux86-64)?

I'm testing it with core-image-weston and modified mesa (to allow
llvmpipe) and with -Bx11-backend.so added to /etc/init.d/weston:

root@qemux86-64:~# /etc/init.d/weston start
Date: 2013-06-05 UTC
[13:47:50.300] weston 1.1.0
               http://wayland.freedesktop.org/
               Bug reports to:
https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.1.0
               Build:  
[13:47:50.308] OS: Linux, 3.8.13-yocto-standard, #1 SMP PREEMPT Tue Jun
4 22:29:53 CEST 2013, x86_64
[13:47:50.311] Loading module '/usr/lib/weston/x11-backend.so'
[13:47:50.317] initializing x11 backend
[13:47:50.318] fatal: failed to create compositor

-- 
Martin 'JaMa' Jansa     jabber: [email protected]

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to