Re: Proposed schedule for 1.14 release

On Mon, Jul 03, 2017 at 09:59:57AM -0700, Bryce Harrington wrote: > Please let me know if there is interest in having a release at this > time. My proposed schedule would be as follows: > > For Wayland 1.14.0 and Weston 2.1.0: Actually on review it should be Weston 3.0.0. I'd still be open

Proposed schedule for 1.14 release

Please let me know if there is interest in having a release at this time. My proposed schedule would be as follows: For Wayland 1.14.0 and Weston 2.1.0: - Alpha on July 11th. Major features done by this point. - Beta on July 25th. - RC1 around August 1st. - Release by August 8th at

Re: [PATCH weston] input: Remove --disable-xkbcommon

Hi Derek, On 28 June 2017 at 17:17, Derek Foreman wrote: > It looks like there are some code paths where this has been forgotten, so > it likely doesn't work as is. It's probable that nobody has actually > used this in a very long time, so it's not worth the maintenance

[libinput] Problem with meson configure

With -Dlibwacom=false, an error occurs. It looks like it is because the definition is inside "if have_libwacom". I'd suggest a fix, but I have no experience with meson to know what the best style would be. meson --prefix=/usr --buildtype=release ../libinput-1.8.0 --libexecdir=/usr/lib \

RE: possible weston bug

I found that. Is it related or about the fix this? https://patchwork.freedesktop.org/patch/148391/   Sorry for noise. Regards.___ wayland-devel mailing list wayland-devel@lists.freedesktop.org

possible weston bug

hi list. It seems like i discovery a weston bug?  I run this program in weston-terminal i get this error log. $ ./a.out i965_dri.so does not support the 0x PCI ID. Segmentation fault (core dumped) $ INTEL_DEVID_OVERRIDE=0x5916 ./a.out [intel_init_bufmgr: 1317] Kernel 3.6 required.

Re: [RFC PATCH wayland-protocols] Introduce logical output protocol for Xwayland

Hi Pekka, > [...] > Maybe more along the lines of xdg_output rather than wp_output. Is > there something else desktops would need about outputs? Identification > (machine-wide unique connector name, output number?) has come up > before, in both human-readable description and persistent >

Re: [RFC PATCH wayland-protocols] Introduce logical output protocol for Xwayland

On Mon, 3 Jul 2017 04:42:52 -0400 (EDT) Olivier Fourdan wrote: > So, 3 possibilities so far: > > 1. Add the logical output in wl_output >Looked like a good idea initially, not so much on further > consideration. pro: It's just an additional event to a existing >

[PATCH wayland 1/3] Pass input/output files as arguments to wayland-scanner

When input/output files are passed as arguments to wayland-scanner, instead of using stdin/stdout, warning and error messages will contain the file name, together with line number, of the warning/error. Doing this helps IDEs jump to the correct line. Signed-off-by: Jonas Ådahl

[PATCH wayland 3/3] tests: Add scanner symbol prefix test

Test that it is possible to implement and use an interface with a symbol prefix. Signed-off-by: Jonas Ådahl --- .gitignore| 5 ++ Makefile.am | 30 +++- tests/symbol-prefix-test-client.c | 77

[PATCH wayland 2/3] scanner: Allow adding a prefix to exported symbols

Two different protocols may use interfaces with identical names. Implementing support for both those protocols would result in symbol clashes, as wayland-scanner generates symbols from the interface names. Make it possible to avoiding these clashes by adding a way to add a prefix to the symbols